Kernel memory corruption via stale transaction reuse
Published Apr 8, 2022 · Updated Aug 3, 2024
Use-after-free in jbd2_journal_wait_updates in Linux kernel 5.17 through 5.17.0 allows local users to corrupt kernel memory. After dropping j_state_lock to sleep, the function reuses a cached j_running_transaction pointer that the commit path can free before the lock is reacquired. Triggering the race requires local low-privileged access and precise timing while JBD2 waits for outstanding filesystem journal updates.
Summary
What happened
Use-after-free in jbd2_journal_wait_updates in Linux kernel 5.17 through 5.17.0 allows local users to corrupt kernel memory. After dropping j_state_lock to sleep, the function reuses a cached j_running_transaction pointer that the commit path can free before the lock is reacquired. Triggering the race requires local low-privileged access and precise timing while JBD2 waits for outstanding filesystem journal updates.
The record
- CVE
- CVE-2022-28796
- Published
- Apr 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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