Local kernel crash via CephFS direct-read assertion
Published Nov 8, 2024 · Updated May 11, 2026
A faulty assertion in affected Linux kernel CephFS releases from 4.2 allows local users to crash the system through direct-I/O reads. The ceph_dirty_folio path executes BUG_ON(ci->i_wr_ref == 0) while a direct-I/O read dirties pages without holding the Fw capability reference. Triggering the assertion requires local access to a mounted CephFS filesystem and causes an availability-only kernel crash.
Summary
What happened
A faulty assertion in affected Linux kernel CephFS releases from 4.2 allows local users to crash the system through direct-I/O reads. The ceph_dirty_folio path executes BUG_ON(ci->i_wr_ref == 0) while a direct-I/O read dirties pages without holding the Fw capability reference. Triggering the assertion requires local access to a mounted CephFS filesystem and causes an availability-only kernel crash.
The record
- CVE
- CVE-2024-50179
- Published
- Nov 8, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 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=4.2
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <11ab19d48ab877430eed0c7d83810970bbcbc4f6
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <126b567a2ef65fc38a71d832bf1216c56816f231
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <74b302ebad5b43ac17460fa58092d892a3cba6eb
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <9d4f619153bab7fa59736462967821d6521a38cb
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <c08dfb1b49492c09cf13838c71897493ea3b424e
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <c26c5ec832dd9e9dcd0a0a892a485c99889b68f0
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <ea98284fc4fb05f276737d2043b02b62be5a8dfb
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <f55e003d261baa7c57d51ae5c8ec1f5c26a35c89
- Affected versionversion=5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 <f863bfd0a2c6c99011c62ea71ac04f8e78707da9
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