LiveActive security incident?Get immediate response
CVE Record

CVE-2024-41035: USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-41035 is a Linux kernel USB handling flaw. A malformed USB endpoint descriptor can make the kernel treat duplicate endpoints as different, creating internal confusion. The public record does not provide CVSS, confirmed impact, or active exploitation evidence.

Executive priority

Handle through normal kernel patch management, with higher priority where untrusted USB devices are common. There is no provided evidence of active exploitation, but kernel USB parsing bugs can matter operationally because they sit below application controls.

Technical view

Linux usbcore assumed reserved bits in bEndpointAddress were zero. When they were not cleared during parsing, endpoint_is_duplicate() could miss duplicate endpoint number and direction pairs. The resolved fix clears reserved bits while parsing copied endpoint descriptors.

Likely exposure

Exposure is most relevant to Linux systems that accept untrusted USB devices or USB passthrough into kernels using affected Linux versions. The source bundle lists Linux as affected and points to stable kernel fixes, but exact distro package exposure requires vendor mapping.

Exploitation context

The bundle cites syzbot discovery and kernel stable fixes. It does not cite KEV listing, public exploitation, exploit availability, or a complete impact statement. Treat active exploitation as not evidenced by the provided sources.

Researcher notes

Focus review on usb_parse_endpoint(), endpoint descriptor copying, bEndpointAddress reserved-bit masking, and duplicate endpoint detection. The source evidence supports malformed descriptor confusion, not broader impacts beyond what the kernel fix text describes.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable usbcore fixes.
  • Use distribution security updates where available, including Debian LTS guidance if applicable.
  • Restrict physical or virtual USB device attachment on sensitive Linux systems.
  • Review vendor advisories for exact fixed package versions.
  • Avoid direct wrangler or deployment actions unrelated to kernel remediation.

Validation and detection

  • Inventory Linux kernel versions on systems that can receive USB devices.
  • Map running kernels to vendor advisories or the referenced stable commits.
  • Confirm distro packages include the usbcore reserved-bit clearing fix.
  • Review USB passthrough exposure in virtualization and appliance environments.
  • Prioritize systems with public kiosks, labs, or unmanaged peripheral access.
Prepared
Confidence
medium
Sources
11

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-41035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, 0a8fd1346254974c3a852338508e4a4cddbb35f1, c3726b442527ab31c7110d0445411f5b5343db01, 15668b4354b38b41b316571deed2763d631b2977, 8597a9245181656ae2ef341906e5f40af323fbca, 264024a2676ba7d91fe7b1713b2c32d1b0b508cb, b0de742a1be16b76b534d088682f18cf57f012d2, 7cc00abef071a8a7d0f4457b7afa2f57f683d83f, 05b0f2fc3c2f9efda47439557e0d51faca7e43ed, 3.2.87, 3.10.106, 3.12.70, 3.16.42, 4.1.39, 4.4.42, 4.9.3unaffected
LinuxLinux4.10, 0, 4.19.318, 5.4.280, 5.10.222, 5.15.163, 6.1.100, 6.6.41, 6.9.10, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.