Kernel memory corruption via unchecked journal length
Published May 20, 2024 · Updated Aug 5, 2026
Out-of-bounds access in bcachefs in Linux 6.7 through 6.8 allows local users to disclose or corrupt kernel memory via a crafted filesystem image. The clean-superblock parser trusts each journal entry's u64s length and advances beyond the section before validating that the next entry remains within bounds. Mounting the image, including through removable-media automount, can expose heap data in kernel logs, corrupt adjacent heap objects, or panic the system.
Summary
What happened
Out-of-bounds access in bcachefs in Linux 6.7 through 6.8 allows local users to disclose or corrupt kernel memory via a crafted filesystem image. The clean-superblock parser trusts each journal entry's u64s length and advances beyond the section before validating that the next entry remains within bounds. Mounting the image, including through removable-media automount, can expose heap data in kernel logs, corrupt adjacent heap objects, or panic the system.
The record
- CVE
- CVE-2024-35948
- Published
- May 20, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-400, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=1c6fdbd8f2465ddfb73a01ec620cbf3d14044e1a <fcdbc1d7a4b638e5d5668de461f320386f3002aa
- Affected versionversion=6.7
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