CVE-2024-45011

char: xillybus: Check USB endpoints when probing device

MEDIUM
5.5
CVSS Score
Published: September 11, 2024 at 03:13 PM UTC
Updated: June 17, 2026 at 07:53 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.14 ≤ v < 5.15.1665.14 ≤ v < 6.1.1075.14 ≤ v < 6.10.75.14 ≤ v < 6.115.14 ≤ v < 6.6.485.16 ≤ v < 6.1.1076.2 ≤ v < 6.6.486.7 ≤ v < 6.10.76.11 rc16.11 rc26.11 rc3a53d1202aef122894b6e46116a92174a9123db5d
Vendor states this is fixed in 1371d32b95972d39c1e6e4bae8b6d0df1b573731 (fixed)
Vendor states this is fixed in 2374bf7558de915edc6ec8cb10ec3291dfab9594 (fixed)
Vendor states this is fixed in 25ee8b2908200fc862c0434e5ad483817d50ceda (fixed)
Vendor states this is fixed in 4267131278f5cc98f8db31d035d64bdbbfe18658 (fixed)
Vendor states this is fixed in 5cff754692ad45d5086b75fef8cc3a99c30a1005 (fixed)
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.166 (unaffected)
Vendor states this is fixed in 6.1.107 (unaffected)
Vendor states this is fixed in 6.10.7 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)
Vendor states this is fixed in 6.6.48 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1371d32b95972d39c1e6e4bae8b6d0df1b573731
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2374bf7558de915edc6ec8cb10ec3291dfab9594
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/25ee8b2908200fc862c0434e5ad483817d50ceda
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4267131278f5cc98f8db31d035d64bdbbfe18658
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5cff754692ad45d5086b75fef8cc3a99c30a1005
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card