nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 46c11be2dca295742a5508ea910a77f7733fb7f4, Kernel 473795610594f261e98920f0945550314df36f07, Kernel 4da07e958bfda2d69d83db105780e8916e3ac02e and 6 more.
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse A syzbot stress test using a corrupted disk image reported that mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or nilfs_palloc_commit_alloc_entry() may output a kernel warning, and can panic if the kernel is booted with panic_on_warn. This is because nilfs2 keeps buffer pointers in local structures for some metadata and reuses them, but such buffers may be forcibly discarded by nilfs_clear_dirty_page() in some critical situations. This issue is reported to appear after commit 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only"), but the issue has potentially existed before. Fix this issue by checking the uptodate flag when attempting to reuse an internally held buffer, and reloading the metadata instead of reusing the buffer if the flag was lost.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=8c26c4e2694a163d525976e804d81cd955bbb40c <46c11be2dca295742a5508ea910a77f7733fb7f4, >=8c26c4e2694a163d525976e804d81cd955bbb40c <473795610594f261e98920f0945550314df36f07, >=8c26c4e2694a163d525976e804d81cd955bbb40c <4da07e958bfda2d69d83db105780e8916e3ac02e, >=8c26c4e2694a163d525976e804d81cd955bbb40c <99a73016a5e12a09586a96f998e91f9ea145cd00, >=8c26c4e2694a163d525976e804d81cd955bbb40c <b308b3eabc429649b5501d36290cea403fbd746c, >=8c26c4e2694a163d525976e804d81cd955bbb40c <b911bef132a06de01a745c6a24172d6db7216333, >=8c26c4e2694a163d525976e804d81cd955bbb40c <cdaac8e7e5a059f9b5e816cda257f08d0abffacd, >=8c26c4e2694a163d525976e804d81cd955bbb40c <d95e403588738c7ec38f52b9f490b15e7745d393, >=8c26c4e2694a163d525976e804d81cd955bbb40c <f1d637b63d8a27ac3386f186a694907f2717fc13 | 46c11be2dca295742a5508ea910a77f7733fb7f4, 473795610594f261e98920f0945550314df36f07, 4da07e958bfda2d69d83db105780e8916e3ac02e, 99a73016a5e12a09586a96f998e91f9ea145cd00, b308b3eabc429649b5501d36290cea403fbd746c, b911bef132a06de01a745c6a24172d6db7216333, cdaac8e7e5a059f9b5e816cda257f08d0abffacd, d95e403588738c7ec38f52b9f490b15e7745d393, f1d637b63d8a27ac3386f186a694907f2717fc13 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket