Kernel crash via uninitialized restart-page free
Published Aug 5, 2022 · Updated Aug 3, 2024
Use-after-free in NTFS3 journal replay in Linux Kernel 5.19 rc1 allows local users to crash the system through a low-memory error. During mount-time log replay, log_read_rst() returns ENOMEM before initializing restart_info, and cleanup passes its uninitialized r_page pointer to kfree(). Triggering the flaw requires local access and an NTFS journal replay under memory pressure; the result is a kernel crash and kernel-memory disclosure.
Summary
What happened
Use-after-free in NTFS3 journal replay in Linux Kernel 5.19 rc1 allows local users to crash the system through a low-memory error. During mount-time log replay, log_read_rst() returns ENOMEM before initializing restart_info, and cleanup passes its uninitialized r_page pointer to kfree(). Triggering the flaw requires local access and an NTFS journal replay under memory pressure; the result is a kernel crash and kernel-memory disclosure.
The record
- CVE
- CVE-2022-1973
- Published
- Aug 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel 5.19 rc1
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
- C reproducer for NTFS3 log_replay invalid freeproof of concept · demonstrated
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