Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-45011char: xillybus: Check USB endpoints when probing device

Description

In the Linux kernel, the following vulnerability has been resolved: char: xillybus: Check USB endpoints when probing device Ensure, as the driver probes the device, that all endpoints that the driver may attempt to access exist and are of the correct type. All XillyUSB devices must have a Bulk IN and Bulk OUT endpoint at address 1. This is verified in xillyusb_setup_base_eps(). On top of that, a XillyUSB device may have additional Bulk OUT endpoints. The information about these endpoints' addresses is deduced from a data structure (the IDT) that the driver fetches from the device while probing it. These endpoints are checked in setup_channels(). A XillyUSB device never has more than one IN endpoint, as all data towards the host is multiplexed in this single Bulk IN endpoint. This is why setup_channels() only checks OUT endpoints.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 20 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-45011, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a53d1202aef122894b6e46116a92174a9123db5d – < 25ee8b2908200fc862c0434e5ad483817d50ceda
    • affected a53d1202aef122894b6e46116a92174a9123db5d – < 4267131278f5cc98f8db31d035d64bdbbfe18658
    • affected a53d1202aef122894b6e46116a92174a9123db5d – < 5cff754692ad45d5086b75fef8cc3a99c30a1005
    • affected a53d1202aef122894b6e46116a92174a9123db5d – < 1371d32b95972d39c1e6e4bae8b6d0df1b573731
    • affected a53d1202aef122894b6e46116a92174a9123db5d – < 2374bf7558de915edc6ec8cb10ec3291dfab9594
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.166 – ≤ 5.15.*
    • unaffected 6.1.107 – ≤ 6.1.*
    • unaffected 6.6.48 – ≤ 6.6.*
    • unaffected 6.10.7 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-45011 badge
[![CVE-2024-45011](https://cveledger.app/badge/CVE-2024-45011.svg)](https://cveledger.app/cve/CVE-2024-45011)

Record last updated .