Review reviewHigh

CVE-2023-54140

Linux

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...

CVSS
7.8
EPSS
0.14%
3.83% percentile
CISA KEV
Not listed
Published
2025.12.24
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

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...

Affected product and versions

Product
Linux
Affected versions
>= 8c26c4e2694a163d525976e804d81cd955bbb40c < 473795610594f261e98920f0945550314df36f07, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < d95e403588738c7ec38f52b9f490b15e7745d393, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 99a73016a5e12a09586a96f998e91f9ea145cd00, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < f1d637b63d8a27ac3386f186a694907f2717fc13, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < b911bef132a06de01a745c6a24172d6db7216333, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 4da07e958bfda2d69d83db105780e8916e3ac02e, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < 46c11be2dca295742a5508ea910a77f7733fb7f4, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < b308b3eabc429649b5501d36290cea403fbd746c, >= 8c26c4e2694a163d525976e804d81cd955bbb40c < cdaac8e7e5a059f9b5e816cda257f08d0abffacd, >= 3.10
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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