System crash via unfinished ST NCI work
Published Apr 12, 2023 · Updated Mar 19, 2025
Use-after-free in the Linux Kernel before 6.3-rc3 allows physically proximate attackers to crash the system during ST NCI device removal. The ndlc_remove path frees ndlc->ndev while llt_ndlc_sm_work can remain scheduled, allowing the worker to pass the freed pointer to nci_recv_frame. Exploitation requires an ST NCI I2C or SPI device and a device-removal race; the bounded consequence is a kernel crash.
Summary
What happened
Use-after-free in the Linux Kernel before 6.3-rc3 allows physically proximate attackers to crash the system during ST NCI device removal. The ndlc_remove path frees ndlc->ndev while llt_ndlc_sm_work can remain scheduled, allowing the worker to pass the freed pointer to nci_recv_frame. Exploitation requires an ST NCI I2C or SPI device and a device-removal race; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2023-1990
- Published
- Apr 12, 2023
- Updated
- Mar 19, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Linux Kernel prior to Kernel 6.3 RC3
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.
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