nilfs2: fix potential bug in end_buffer_async_write
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f3e4963566f58726d3265a727116a42b591f6596, Kernel 3.11, Kernel 3.12 and 16 more.
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buffers() and nilfs_lookup_node_buffers() and the resulting crash. This modification is safe as long as it is used for file data and b-tree node blocks where the page caches are independent. However, it was irrelevant and redundant to also introduce async_write for segment summary and super root blocks that share buffers with the backing device. This led to the possibility that the BUG_ON check in end_buffer_async_write would fail as described above, if independent writebacks of the backing device occurred in parallel. The use of async_write for segment summary buffers has already been removed in a previous change. Fix this issue by removing the manipulation of the async_write flag for the remaining super root block buffer.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <f3e4963566f58726d3265a727116a42b591f6596, >=3.10.16 <3.11, >=3.11.5 <3.12, >=3.2.52 <3.3, >=3.4.83 <3.5, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <2c3bdba00283a6c7a5b19481a59a730f46063803, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <5bc09b397cbf1221f8a8aacb1152650c9195b02b, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <626daab3811b772086aef1bf8eed3ffe6f523eff, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <6589f0f72f8edd1fa11adce4eedbd3615f2e78ab, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <8fa90634ec3e9cc50f42dd605eec60f2d146ced8, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <c4a09fdac625e64abe478dcf88bfa20406616928, >=7f42ec3941560f0902fe3671e36f2c20ffd3af0a <d31c8721e816eff5ca6573cc487754f357c093cd, =3.12, =831c87640d23ccb253a02e4901bd9a325b5e8c2d, =8f67918af09fc0ffd426a9b6f87697976d3fbc7b, =ccebcc74c81d8399c7b204aea47c1f33b09c2b17, =d8974c7fe717ee8fb0706e35cc92e0bcdf660ec5 | f3e4963566f58726d3265a727116a42b591f6596, 3.11, 3.12, 3.3, 3.5, 2c3bdba00283a6c7a5b19481a59a730f46063803, 5bc09b397cbf1221f8a8aacb1152650c9195b02b, 626daab3811b772086aef1bf8eed3ffe6f523eff, 6589f0f72f8edd1fa11adce4eedbd3615f2e78ab, 8fa90634ec3e9cc50f42dd605eec60f2d146ced8, c4a09fdac625e64abe478dcf88bfa20406616928, d31c8721e816eff5ca6573cc487754f357c093cd |
| linux-kernel: Kernel | >=3.11.5 <3.12, >=3.12.0 <4.19.307, >=3.2.52 <3.3, >=3.4.83 <3.5, >=4.20.0 <5.4.269, >=5.11.0 <5.15.149, >=5.16.0 <6.1.79, >=5.5.0 <5.10.210, >=6.2.0 <6.6.18, >=6.7.0 <6.7.6, >=3.10.16 <3.11 | 3.12, 4.19.307, 3.3, 3.5, 5.4.269, 5.15.149, 6.1.79, 5.10.210, 6.6.18, 6.7.6, 3.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket