Kernel-memory corruption via PCMCIA removal race
Published Oct 30, 2022 · Updated Aug 3, 2024
Race condition in the Linux kernel through 6.0.6 allows physically proximate attackers to corrupt kernel memory through the SCR24x driver. scr24x_remove() can free driver state while scr24x_open() concurrently opens the device, causing the open path to access released memory. Exploitation requires physical removal of a PCMCIA device during open(), and public records do not document a demonstrated privilege-gain or code-execution path.
Summary
What happened
Race condition in the Linux kernel through 6.0.6 allows physically proximate attackers to corrupt kernel memory through the SCR24x driver. scr24x_remove() can free driver state while scr24x_open() concurrently opens the device, causing the open path to access released memory. Exploitation requires physical removal of a PCMCIA device during open(), and public records do not document a demonstrated privilege-gain or code-execution path.
The record
- CVE
- CVE-2022-44034
- Published
- Oct 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- 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?
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