Kernel memory access via PCMCIA detach race
Published Oct 30, 2022 · Updated Aug 3, 2024
Use-after-free in the Linux kernel through 6.0.6 allows physically proximate attackers to access freed memory by racing PCMCIA removal with open(). The cm4000_cs driver's cmm_open() can retain a device pointer while cm4000_detach() frees the associated structure, leaving the acquired descriptor dangling. Exploitation requires physical PCMCIA access and precise timing; a subsequent read dereferences the freed kernel object.
Summary
What happened
Use-after-free in the Linux kernel through 6.0.6 allows physically proximate attackers to access freed memory by racing PCMCIA removal with open(). The cm4000_cs driver's cmm_open() can retain a device pointer while cm4000_detach() frees the associated structure, leaving the acquired descriptor dangling. Exploitation requires physical PCMCIA access and precise timing; a subsequent read dereferences the freed kernel object.
The record
- CVE
- CVE-2022-44032
- Published
- Oct 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 30, 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=0 <=6.0.6
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