System crash via unfinished EMAC removal work
Published May 18, 2023 · Updated May 5, 2025
Use-after-free in the Qualcomm EMAC driver in the Linux kernel before 6.2.9 allows physically proximate attackers to crash the system. The emac_remove function frees the network device without first canceling work started by the timeout or interrupt handlers, allowing emac_work_thread to access the freed device. Exploitation requires physical device removal or privileged driver unbinding; the demonstrated consequence is a system crash.
Summary
What happened
Use-after-free in the Qualcomm EMAC driver in the Linux kernel before 6.2.9 allows physically proximate attackers to crash the system. The emac_remove function frees the network device without first canceling work started by the timeout or interrupt handlers, allowing emac_work_thread to access the freed device. Exploitation requires physical device removal or privileged driver unbinding; the demonstrated consequence is a system crash.
The record
- CVE
- CVE-2023-33203
- Published
- May 18, 2023
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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.
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