Kernel panic via stale metadata buffer reuse
Published Dec 24, 2025 · Updated Dec 24, 2025
Improper buffer reuse in affected Linux nilfs2 kernels allows local users to panic the kernel through a corrupted disk image. nilfs2 retains metadata-buffer pointers after nilfs_clear_dirty_page() discards them, then passes a non-uptodate buffer to mark_buffer_dirty() instead of reloading metadata. A corrupted nilfs2 volume and local filesystem operations are required; panic_on_warn turns the warning into a kernel panic, while stale allocator metadata can expose or corrupt files.
Summary
What happened
Improper buffer reuse in affected Linux nilfs2 kernels allows local users to panic the kernel through a corrupted disk image. nilfs2 retains metadata-buffer pointers after nilfs_clear_dirty_page() discards them, then passes a non-uptodate buffer to mark_buffer_dirty() instead of reloading metadata. A corrupted nilfs2 volume and local filesystem operations are required; panic_on_warn turns the warning into a kernel panic, while stale allocator metadata can expose or corrupt files.
The record
- CVE
- CVE-2023-54140
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.10
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <46c11be2dca295742a5508ea910a77f7733fb7f4
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <473795610594f261e98920f0945550314df36f07
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <4da07e958bfda2d69d83db105780e8916e3ac02e
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <99a73016a5e12a09586a96f998e91f9ea145cd00
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <b308b3eabc429649b5501d36290cea403fbd746c
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <b911bef132a06de01a745c6a24172d6db7216333
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <cdaac8e7e5a059f9b5e816cda257f08d0abffacd
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <d95e403588738c7ec38f52b9f490b15e7745d393
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <f1d637b63d8a27ac3386f186a694907f2717fc13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- syzbot C and syz reproducers for WARNING in mark_buffer_dirtyproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo