Skip to content
Noroxi
CVE-2024-45006· NVD / CVE Program· CNA Linux

xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0f0654318e25b2c185e245ba4a591e42fabb5e59, 365ef7c4277fdd781a695c3553fa157d622d805d, 5ad898ae82412f8a689d59829804bff2999dd0ea.

Low priority for now. Upgrade to Linux Linux 0f0654318e25b2c185e245ba4a591e42fabb5e59, 365ef7c4277fdd781a695c3553fa157d622d805d, 5ad898ae82412f8a689d59829804bff2999dd0ea or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration re-enumerating full-speed devices after a failed address device command can trigger a NULL pointer dereference. Full-speed devices may need to reconfigure the endpoint 0 Max Packet Size value during enumeration. Usb core calls usb_ep0_reinit() in this case, which ends up calling xhci_configure_endpoint(). On Panther point xHC the xhci_configure_endpoint() function will additionally check and reserve bandwidth in software. Other hosts do this in hardware If xHC address device command fails then a new xhci_virt_device structure is allocated as part of re-enabling the slot, but the bandwidth table pointers are not set up properly here. This triggers the NULL pointer dereference the next time usb_ep0_reinit() is called and xhci_configure_endpoint() tries to check and reserve bandwidth [46710.713538] usb 3-1: new full-speed USB device number 5 using xhci_hcd [46710.713699] usb 3-1: Device not responding to setup address. [46710.917684] usb 3-1: Device not responding to setup address. [46711.125536] usb 3-1: device not accepting address 5, error -71 [46711.125594] BUG: kernel NULL pointer dereference, address: 0000000000000008 [46711.125600] #PF: supervisor read access in kernel mode [46711.125603] #PF: error_code(0x0000) - not-present page [46711.125606] PGD 0 P4D 0 [46711.125610] Oops: Oops: 0000 [#1] PREEMPT SMP PTI [46711.125615] CPU: 1 PID: 25760 Comm: kworker/1:2 Not tainted 6.10.3_2 #1 [46711.125620] Hardware name: Gigabyte Technology Co., Ltd. [46711.125623] Workqueue: usb_hub_wq hub_event [usbcore] [46711.125668] RIP: 0010:xhci_reserve_bandwidth (drivers/usb/host/xhci.c Fix this by making sure bandwidth table pointers are set up correctly after a failed address device command, and additionally by avoiding checking for bandwidth in cases like this where no actual endpoints are added or removed, i.e. only context for default control endpoint 0 is evaluated.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 4, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-45006

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.15 and later · before 4.19.321
  • linux linux kernel4.20 and later · before 5.4.283
  • linux linux kernel5.5 and later · before 5.10.225
  • linux linux kernel5.11 and later · before 5.15.166
  • linux linux kernel5.16 and later · before 6.1.107
  • linux linux kernel6.2 and later · before 6.6.48
  • linux linux kernel6.7 and later · before 6.10.7
  • linux linux kernel6.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.15affected
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before ef0a0e616b2789bb804a0ce5e161db03170a85b6affected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before a57b0ebabe6862dce0a2e0f13e17941ad72fc56baffected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before 0f0654318e25b2c185e245ba4a591e42fabb5e59affected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before 365ef7c4277fdd781a695c3553fa157d622d805daffected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before 5ad898ae82412f8a689d59829804bff2999dd0eaaffected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before 6b99de301d78e1f5249e57ef2c32e1dec3df2bb1affected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before 8fb9d412ebe2f245f13481e4624b40e651570cbdaffected · git
    • 651aaf36a7d7b36a58980e70133f9437d4f6d312 and later · before af8e119f52e9c13e556be9e03f27957554a84656affected · git
    • before 4.15not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.112-16.1.112-1
Debian:13linuxbefore 6.10.7-16.10.7-1

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-45004Sep 4, 2024 · KEYS: trusted: dcp: fix leak of blob encryption key
    22Monitor
  • ← EarlierCVE-2024-45005Sep 4, 2024 · KVM: s390: fix validity interception issue when gisa is switched off
    22Monitor
  • Later →CVE-2024-45007Sep 4, 2024 · char: xillybus: Don't destroy workqueue from work item running on it
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f0654318e25b2c185e245ba4a591e42fabb5e59Vendor (CNA)
Linux Linux365ef7c4277fdd781a695c3553fa157d622d805dVendor (CNA)
Linux Linux5ad898ae82412f8a689d59829804bff2999dd0eaVendor (CNA)
Linux Linux6b99de301d78e1f5249e57ef2c32e1dec3df2bb1Vendor (CNA)
Linux Linux8fb9d412ebe2f245f13481e4624b40e651570cbdVendor (CNA)
Linux Linuxa57b0ebabe6862dce0a2e0f13e17941ad72fc56bVendor (CNA)
Linux Linuxaf8e119f52e9c13e556be9e03f27957554a84656Vendor (CNA)
Linux Linuxef0a0e616b2789bb804a0ce5e161db03170a85b6Vendor (CNA)
debian:linux6.1.112-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records