Local denial of service via stale buffer flag
Published Nov 5, 2024 · Updated May 11, 2026
Denial of service in the Linux nilfs2 driver allows local users to trigger a kernel BUG via a corrupted filesystem image. The nilfs2 page-clearing path discards a page, folio, or buffer head without clearing its buffer-delay flag, leaving submit_bh_wbc() to encounter an invalid delayed-buffer state. When the kernel reads the corrupted image and degrades the filesystem to read-only, the stale flag can trip the BUG_ON check and interrupt system availability; normal log writing does not create the inconsistency.
Summary
What happened
Denial of service in the Linux nilfs2 driver allows local users to trigger a kernel BUG via a corrupted filesystem image. The nilfs2 page-clearing path discards a page, folio, or buffer head without clearing its buffer-delay flag, leaving submit_bh_wbc() to encounter an invalid delayed-buffer state. When the kernel reads the corrupted image and degrades the filesystem to read-only, the stale flag can trip the BUG_ON check and interrupt system availability; normal log writing does not create the inconsistency.
The record
- CVE
- CVE-2024-50116
- Published
- Nov 5, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 5, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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 <033bc52f35868c2493a2d95c56ece7fc155d7cb3
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <27524f65621f490184f2ace44cd8e5f3685af4a3
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <412a30b1b28d6073ba29c46a2b0f324c5936293f
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <6ed469df0bfbef3e4b44fca954a781919db9f7ab
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <743c78d455e784097011ea958b27396001181567
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <822203f6355f4b322d21e7115419f6b98284be25
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <9f2ab98371c2f2488bf3bf3f9b2a73510545e9c1
- Affected versionversion=8c26c4e2694a163d525976e804d81cd955bbb40c <c6f58ff2d4c552927fe9a187774e668ebba6c7aa
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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