Kernel crash via invalid NILFS2 buffer-head dereference
Published Oct 21, 2024 · Updated May 11, 2026
NULL pointer dereference in affected Linux kernel builds before 6.1 allows local users to crash the kernel via corrupted NILFS2 DAT metadata. During a cascading b-tree update, nilfs_dat_commit_end calls nilfs_dat_commit_free with invalid pr_desc_bh and pr_bitmap_bh buffer heads, which nilfs_palloc_commit_free_entry dereferences. The path requires corrupted on-disk DAT metadata and interrupts the host without reported disclosure or data modification.
Summary
What happened
NULL pointer dereference in affected Linux kernel builds before 6.1 allows local users to crash the kernel via corrupted NILFS2 DAT metadata. During a cascading b-tree update, nilfs_dat_commit_end calls nilfs_dat_commit_free with invalid pr_desc_bh and pr_bitmap_bh buffer heads, which nilfs_palloc_commit_free_entry dereferences. The path requires corrupted on-disk DAT metadata and interrupts the host without reported disclosure or data modification.
The record
- CVE
- CVE-2022-49007
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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=2.6.30
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <165c7a3b27a3857ebf57f626b9f38b48b6792e68
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <2f2c59506ae39496588ceb8b88bdbdbaed895d63
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <33021419fd81efd3d729a7f19341ba4b98fe66ce
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <381b84f60e549ea98cec4666c6c728b1b3318756
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <9a130b72e6bd1fb07fc3cde839dc6fb53da76f07
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <bc3fd3293887b4cf84a9109700faeb82de533c89
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <e858917ab785afe83c14f5ac141301216ccda847
- Affected versionversion=a17564f58b11476c011d623fa1f268602a81c27c <f0a0ccda18d6fd826d7c7e7ad48a6ed61c20f8b4
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.
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