Skip to content
Fencer Vulns
medium 5.5

CVE-2024-45011 json

char: xillybus: Check USB endpoints when probing device

published 2024-09-11 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-41616

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 5.15.166, 6.1.107, 6.6.48, 6.10.7, 6.11
  • linux Debian 12 6.1.112-1
  • linux Debian 14, Debian 13 6.10.7-1

debian advisories DEBIAN-CVE-2024-45011

  • linux Ubuntu 22.04 LTS 5.15.0-125.135
  • linux Ubuntu 24.04 LTS 6.8.0-50.51
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1072.78
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1020.22
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1071.79
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1019.21
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1069.75
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1015.19

ubuntu advisories UBUNTU-CVE-2024-45011

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Linux Micro 6.0 6.4.0-11.1
  • kernel-source-rt Linux Micro 6.0 6.4.0-11.1
  • kernel-livepatch-MICRO-6-0-RT_Update_3 Linux Micro 6.0 1-1.2
  • kernel-source Linux Micro 6.0 6.4.0-20.1
  • kernel-default Linux Micro 6.0 6.4.0-20.1
  • kernel-kvmsmall Linux Micro 6.0 6.4.0-20.1
  • kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
  • kernel-livepatch-MICRO-6-0_Update_3 Linux Micro 6.0 1-1.2

suse advisories SUSE-SU-2025:20077-1SUSE-SU-2025:20073-1SUSE-SU-2024:3592-1SUSE-SU-2024:3587-1SUSE-SU-2024:3569-1SUSE-SU-2024:3564-1

  • kernel CBL-Mariner 2.0 5.15.167.1-1
  • kernel Azure Linux 3.0 6.6.51.1-1

azure linux advisories AZL-49203AZL-49254

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-45011 updated cvss 5.5

kernel: char: xillybus: Check USB endpoints when probing device

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.