CVE-2023-54140

HIGHCVSS 7.8/10EPSS 0.20%

Last modified

CVE-2023-54140 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.20%

10.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8c26c4e2694a163d525976e804d81cd955bbb40c, < 473795610594f261e98920f0945550314df36f07; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < d95e403588738c7ec38f52b9f490b15e7745d393; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < 99a73016a5e12a09586a96f998e91f9ea145cd00; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < f1d637b63d8a27ac3386f186a694907f2717fc13; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < b911bef132a06de01a745c6a24172d6db7216333; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < 4da07e958bfda2d69d83db105780e8916e3ac02e; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < 46c11be2dca295742a5508ea910a77f7733fb7f4; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < b308b3eabc429649b5501d36290cea403fbd746c; >= 8c26c4e2694a163d525976e804d81cd955bbb40c, < cdaac8e7e5a059f9b5e816cda257f08d0abffacd
LinuxLinux3.10

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2023-54140?
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.
How severe is CVE-2023-54140?
CVE-2023-54140 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.
How do I fix CVE-2023-54140?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

Are you affected by CVE-2023-54140?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST