dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-41721

HIGH · 8.1 CVSS v3.1 Published 2024-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An insufficient boundary validation in the USB code could lead to an out-of-bounds read on the heap, which could potentially lead to an arbitrary write and remote code execution.

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 · moderate confidence

Insufficient boundary validation in USB code enables a heap-based out-of-bounds read, which can be chained to achieve arbitrary write operations and ultimately remote code execution.

MitigationApply vendor-supplied patches for the USB stack; until then, restrict USB device exposure and monitor for anomalous USB device enumeration patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify USB stack components
    List running processes and loaded kernel modules related to USB. On Linux: lsmod | grep -i usb; on Windows: sc query type= service state= all | findstr -i usb
    Affected if USB kernel modules or services are loaded/running on the system
  2. Check USB service status
    On Windows: sc query USB_SERVICE_NAME; on Linux: systemctl list-units --type=service | grep -i usb or check /proc/bus/usb
    Affected if USB services are enabled and running
  3. Detect USB device enumeration
    On Linux: lsusb or check /dev/bus/usb; on Windows: Get-PnpDevice -Class USB or device manager enumeration
    Affected if USB devices can be enumerated, indicating the USB stack is active
  4. Identify USB driver/kernel module versions
    On Linux: modinfo <usb_module_name> for version info; on Windows: driverquery /v | findstr -i usb
    Affected if USB drivers are present without recent patching
  5. Check for USB stack in embedded/network products
    Review firmware or software manifests for USB stack library versions (e.g., libusb, USB device drivers, USB host stack)
    Affected if The product includes USB functionality in its codebase

A system is affected if it runs any USB stack code that has not been patched and exposes USB device handling functionality to potentially untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for the USB stack; until then, restrict USB device exposure and monitor for anomalous USB device enumeration patterns.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41721 — 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-41721 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