dbcve.org
Linux KernelOperating system · Linux

CVE-2024-45011

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-11
Fix available
A fix is available. Upgrade to 5.15.166 / 6.1.107 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: 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.

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:>= 5.14, < 5.15.166>= 5.16, < 6.1.107>= 6.2, < 6.6.48>= 6.7, < 6.10.7= 6.11

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 5.15.166 / 6.1.107 / 6.6.48 or later
Fixed in 5.15.1666.1.1076.6.48
Vendor patch git.kernel.org →
Recommended fix High confidence

5.15.166 (for 5.14-5.15.x) or 6.1.107 (for 5.16-6.1.x) or 6.6.48 (for 6.2-6.6.x) or 6.10.7 (for 6.7-6.10.x)

  1. Identify the currently running kernel version using 'uname -r'
  2. Determine which major kernel branch is in use (e.g., 5.15, 6.1, 6.6, or 6.10)
  3. Update package repositories: 'apt update' (Debian/Ubuntu) or 'yum/dnf check-update' (RHEL/Fedora)
  4. Upgrade the kernel to the fixed release for your branch: For 5.15.x systems, upgrade to 5.15.166 or later; For 6.1.x systems, upgrade to 6.1.107 or later; For 6.2-6.6.x systems, upgrade to 6.6.48 or later; For 6.7-6.10.x systems, upgrade to 6.10.7 or later
  5. Reboot the system to load the new kernel: 'systemctl reboot'
  6. Verify the new kernel version after reboot using 'uname -r'
Caveat Kernel upgrades may require reboot and could have compatibility implications with custom kernel modules or specific hardware drivers; ensure critical applications are tested on the new kernel before production deployment

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-45011 — 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-45011 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