CVE-2024-43883: usb: vhci-hcd: Do not drop references before new references are gained
In the Linux kernel, the following vulnerability has been resolved:
usb: vhci-hcd: Do not drop references before new references are gained
At a few places the driver carries stale pointers
to references that can still be used. Make sure that does not happen.
This strictly speaking closes ZDI-CAN-22273, though there may be
similar races in the driver.
Security readout for executives and security teams
Plain-English summary
A race in Linux’s vhci-hcd USB driver can leave references pointing at stale objects. The supplied record assigns a critical 9.8 score and indicates possible confidentiality, integrity, and availability impact, but it does not establish practical attack prerequisites or observed exploitation.
Executive priority
Require an urgent exposure assessment and expedited patching where vhci-hcd is active. Systems without the driver or with confirmed vendor fixes are lower priority. Do not treat the 9.8 score alone as proof of widespread remote exploitability.
Technical view
The driver releases references before replacement references are secured, creating windows where stale pointers may remain usable. Upstream stable commits correct the reference ordering across multiple kernel branches. The record warns similar races may exist, so this fix may not address every related condition.
Likely exposure
Potential exposure is limited to systems running affected Linux kernel builds with the vhci-hcd driver available or active. The bundle provides no CPEs, and its mixed version and commit data require vendor-specific verification. Distribution backports may make version-only scanning unreliable.
Exploitation context
CISA KEV status is false, and the supplied sources do not report active exploitation or a public exploit. The issue is associated with ZDI-CAN-22273, indicating prior vulnerability research, but the bundle does not document proven attack paths. Network exploitability should not be assumed solely from the CVSS vector.
Researcher notes
The record supplies no CWE, CPE, detailed trigger conditions, or demonstrated exploitation outcome. Multiple stable commits reflect branch-specific backports. Researchers should examine reference-lifetime transitions and adjacent race windows, since the upstream description explicitly says similar races may remain, without assuming they are independently exploitable.
Mitigation direction
Apply a supported vendor kernel update that incorporates the applicable upstream stable fix.
Check distribution advisories and package changelogs because vendors may backport fixes without changing major kernel versions.
If updating is delayed, consult vendor guidance about safely disabling unused vhci-hcd functionality.
Reboot after kernel replacement so the corrected kernel is actually running.
Validation and detection
Record the running kernel version and compare it with vendor CVE or package guidance.
Determine whether vhci-hcd is built, installed, loaded, or operationally required.
Verify the installed kernel package maps to an upstream fixing commit or documented vendor backport.
After rebooting, confirm the corrected kernel is active rather than merely installed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-43883 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.