dbcve.org
Linux KernelOperating system · Linux

CVE-2024-41035

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-29
Fix available
A fix is available. Upgrade to 3.3 / 3.11 or later.
See remediation →
57/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: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor Syzbot has identified a bug in usbcore (see the Closes: tag below) caused by our assumption that the reserved bits in an endpoint descriptor's bEndpointAddress field will always be 0. As a result of the bug, the endpoint_is_duplicate() routine in config.c (and possibly other routines as well) may believe that two descriptors are for distinct endpoints, even though they have the same direction and endpoint number. This can lead to confusion, including the bug identified by syzbot (two descriptors with matching endpoint numbers and directions, where one was interrupt and the other was bulk). To fix the bug, we will clear the reserved bits in bEndpointAddress when we parse the descriptor. (Note that both the USB-2.0 and USB-3.1 specs say these bits are "Reserved, reset to zero".) This requires us to make a copy of the descriptor earlier in usb_parse_endpoint() and use the copy instead of the original when checking for duplicates.

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

A detailed technical summary for this CVE is being prepared.

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:>= 3.2.87, < 3.3>= 3.10.106, < 3.11>= 3.12.70, < 3.13>= 3.16.42, < 3.17>= 4.1.39, < 4.2>= 4.4.42, < 4.5>= 4.9.3, < 4.10>= 4.10.1, < 4.19.318>= 4.20, < 5.4.280>= 5.5, < 5.10.222>= 5.11, < 5.15.163>= 5.16, < 6.1.100

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 3.3 / 3.11 / 3.13 or later
Fixed in 3.33.113.13
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to one of: Linux 3.3, 3.11, 3.13, or 3.17 (or newer LTS branch such as 4.x, 5.x, or later)

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Match the current kernel to the affected version range: 3.2.x, 3.10.x, 3.12.x, or 3.16.x
  3. 3. Upgrade to the next stable release in that kernel branch: for 3.2.x upgrade to >=3.3, for 3.10.x upgrade to >=3.11, for 3.12.x upgrade to >=3.13, or for 3.16.x upgrade to >=3.17
  4. 4. Alternatively, upgrade to a newer LTS kernel branch (4.x, 5.x, or later) which includes this fix
  5. 5. After upgrade, verify the kernel version with `uname -r` and confirm the fix commit 2bd8534a1b83 is included
  6. 6. Reboot the system to load the new kernel
Caveat Low risk: This is a bug fix that clears reserved bits in USB endpoint descriptors per USB specification; it should not break functionality but may reveal previously masked configuration issues

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 $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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