dbcve.org
Linux KernelOperating system · Linux

CVE-2024-43883

HIGH · 7.0 CVSS v3.1 Published 2024-08-23
Fix available
A fix is available. Upgrade to 4.19.320 / 5.4.282 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:< 4.19.320>= 4.20, < 5.4.282>= 5.5, < 5.10.224>= 5.11, < 5.15.165>= 5.16, < 6.1.105>= 6.2, < 6.6.46>= 6.7, < 6.10.5= 6.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.19.320 / 5.4.282 / 5.10.224 or later
Fixed in 4.19.3205.4.2825.10.224
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel >= 5.15.165 (or >= 5.10.224, >= 5.4.282, or >= 4.19.320 depending on your current branch)

  1. Identify the current running kernel version using `uname -r`
  2. Check if the current version is among the affected versions: < 4.19.320, >= 4.20 and < 5.4.282, >= 5.5 and < 5.10.224, or >= 5.11 and < 5.15.165
  3. Update the system package repository to fetch the latest available kernel packages
  4. Install a kernel version >= 5.15.165 (or the latest available in your distribution's stable repository) using the distribution's package manager (e.g., `apt update && apt upgrade` for Debian/Ubuntu, `yum update` for RHEL/CentOS, or `pacman -Syu` for Arch)
  5. Reboot the system to load the new kernel
  6. Verify the system is running a patched kernel version using `uname -r` and confirm it is >= 5.15.165 (or the appropriate minimum for your branch)
Caveat Kernel upgrades may require rebuilding out-of-tree kernel modules; ensure proprietary drivers (e.g., NVIDIA, VirtualBox) are compatible with the new kernel before rebooting

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43883 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43883 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data