CVE-2024-45011
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 5.15.166
- Linux Kernel < 6.1.107
- Linux Kernel < 6.6.48
- Linux Kernel < 6.10.7
- Linux Kernel 6.11
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-45011.md and follow it. Check whether this project is affected by CVE-2024-45011. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1371d32b95972d39c1e6e4bae8b6d0df1b573731
- https://git.kernel.org/stable/c/2374bf7558de915edc6ec8cb10ec3291dfab9594
- https://git.kernel.org/stable/c/25ee8b2908200fc862c0434e5ad483817d50ceda
- https://git.kernel.org/stable/c/4267131278f5cc98f8db31d035d64bdbbfe18658
- https://git.kernel.org/stable/c/5cff754692ad45d5086b75fef8cc3a99c30a1005
References
- https://git.kernel.org/stable/c/1371d32b95972d39c1e6e4bae8b6d0df1b573731
- https://git.kernel.org/stable/c/2374bf7558de915edc6ec8cb10ec3291dfab9594
- https://git.kernel.org/stable/c/25ee8b2908200fc862c0434e5ad483817d50ceda
- https://git.kernel.org/stable/c/4267131278f5cc98f8db31d035d64bdbbfe18658
- https://git.kernel.org/stable/c/5cff754692ad45d5086b75fef8cc3a99c30a1005
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html