Use-after-free via concurrent VCC device removal
Published Feb 22, 2023 · Updated Mar 20, 2025
Race condition in the Linux kernel VCC driver through 6.2.0-rc2 allows physically proximate attackers to trigger a use-after-free. vcc_remove() frees the vcc_port structure while vcc_open() can still dereference it because removal does not wait for the open reference to close. Exploitation requires physical access to remove a VCC device concurrently with open(), and public sources do not specify the resulting system behavior beyond the use-after-free condition.
Summary
What happened
Race condition in the Linux kernel VCC driver through 6.2.0-rc2 allows physically proximate attackers to trigger a use-after-free. vcc_remove() frees the vcc_port structure while vcc_open() can still dereference it because removal does not wait for the open reference to close. Exploitation requires physical access to remove a VCC device concurrently with open(), and public sources do not specify the resulting system behavior beyond the use-after-free condition.
The record
- CVE
- CVE-2023-23039
- Published
- Feb 22, 2023
- Updated
- Mar 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2023CVE publishedPublication date reported by the CVE source.
- Mar 20, 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