Kernel crash via unlocked journal-abort check
Published Jun 18, 2025 · Updated May 11, 2026
Reachable assertion in the Linux kernel allows local users to crash the kernel through concurrent ext4 unlink activity. The jbd2_journal_dirty_metadata function checks whether its handle is aborted before taking jh->b_state_lock, allowing a concurrent journal abort and buffer refile to leave b_frozen_data populated when the assertion runs. Exploitation requires low-privileged local access and a timing-sensitive ext4 journal-abort race; the reported consequence is a kernel BUG and service interruption.
Summary
What happened
Reachable assertion in the Linux kernel allows local users to crash the kernel through concurrent ext4 unlink activity. The jbd2_journal_dirty_metadata function checks whether its handle is aborted before taking jh->b_state_lock, allowing a concurrent journal abort and buffer refile to leave b_frozen_data populated when the assertion runs. Exploitation requires low-privileged local access and a timing-sensitive ext4 journal-abort race; the reported consequence is a kernel BUG and service interruption.
The record
- CVE
- CVE-2022-50126
- Published
- Jun 18, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-617, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 18, 2025CVE 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.19
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <0f61c6dc4b714be9d79cf0782ca02ba01c1b7ac3
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <4a734f0869f970b8a9b65062ea40b09a5da9dba8
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <6073389db83b903678a0920554fa19f5bdc51c48
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <731c1662d838fe954c6759e3ee43229b0d928fe4
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <ddd896792e1718cb84c96f3e618270589b6886dc
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <e62f79827784f56499a50ea2e893c98317b5407b
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <f7161d0da975adc234161cd0641d0e484f5ce375
- Affected versionversion=470decc613ab2048b619a01028072d932d9086ee <fa5b65d39332fef7a11ae99cb1f0696012a61527
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.
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