udf: don't use eloc after the end of the unallocated space table
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7, Kernel 0ceb311c0f7af4f4b38fc1066178b84a60d61a05, Kernel 812d49a09ce0a8fcc784349d6a95e975a4af51cf and 4 more.
In the Linux kernel, the following vulnerability has been resolved: udf: don't use eloc after the end of the unallocated space table When udf_next_aext() returns 0, its eloc, elen and etype outputs hold no defined value. Two walks of the unallocated space table still use eloc after the walk has reached the end of the table. udf_table_prealloc_blocks() looks for a free extent starting at first_block and decides whether it found one by comparing eloc with first_block after the walk. If the table's list ends in a continuation descriptor that leads to an empty allocation extent, eloc is then the block of that allocation extent, which is in use, and if that is first_block, the block is handed out as preallocation. Once udf_discard_prealloc() no longer frees the wrong block, this is what still makes fsx in generic/091 and generic/263 read back bad data on a table, in about one run in four. Only take the extent if the walk stopped at it. When udf_table_free_blocks() cannot merge the freed blocks into an existing extent, it appends a new one and sets only its block number, so the partition reference comes from whatever eloc held after the walk, and with long allocation descriptors it is written to disk. For a table without extents, eloc was never set. Take the partition reference from the freed blocks instead. Short allocation descriptors do not store the partition reference, which is why this half remains a latent long-descriptor fix rather than a reproduced failure.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0ceb311c0f7af4f4b38fc1066178b84a60d61a05, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <812d49a09ce0a8fcc784349d6a95e975a4af51cf, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <94401199df90e1c2a50c6e4b73618ac5a4ba83ba, =2.6.12 | 9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7, 0ceb311c0f7af4f4b38fc1066178b84a60d61a05, 812d49a09ce0a8fcc784349d6a95e975a4af51cf, 94401199df90e1c2a50c6e4b73618ac5a4ba83ba |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=2.6.12 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket