LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26716: usb: core: Prevent null pointer dereference in update_port_device_state

In the Linux kernel, the following vulnerability has been resolved: usb: core: Prevent null pointer dereference in update_port_device_state Currently, the function update_port_device_state gets the usb_hub from udev->parent by calling usb_hub_to_struct_hub. However, in case the actconfig or the maxchild is 0, the usb_hub would be NULL and upon further accessing to get port_dev would result in null pointer dereference. Fix this by introducing an if check after the usb_hub is populated.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26716 is a Linux kernel USB core flaw that can trigger a null pointer dereference during USB port state updates. In practical terms, the most defensible business concern from the provided sources is system instability or crash risk, especially on machines exposed to untrusted USB devices. Severity and exploitability are not scored in the bundle.

Executive priority

Handle through normal kernel patch management, with faster action for kiosks, workstations, labs, and other systems where untrusted USB devices may be attached. Current evidence supports availability concern, not confirmed remote compromise or active exploitation.

Technical view

The flaw is in update_port_device_state. The code derives a usb_hub from udev->parent, but when actconfig or maxchild is 0, that hub can be NULL. Later access to port_dev can dereference NULL. The listed kernel fix adds a NULL check after usb_hub is populated.

Likely exposure

Likely exposure is Linux systems running affected kernel versions in the USB core path. Risk is most relevant where physical or logical USB device attachment is possible. The bundle does not identify affected distributions, appliances, package versions, or network-reachable attack paths.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. No public exploit status, CVSS vector, CWE, privilege requirement, or attack complexity is provided. Treat exploitability as unconfirmed from this bundle.

Researcher notes

Evidence is limited to the CVE description and Linux stable references. The affected-version data in the bundle is sparse and not distribution-specific. Do not infer remote exploitability, privilege boundaries, or fixed package names without vendor confirmation.

Mitigation direction

  • Check Linux kernel and distribution vendor guidance for patched builds.
  • Update to a kernel release containing the referenced stable fixes.
  • Prioritize systems exposed to untrusted USB peripherals or public physical access.
  • Restrict unnecessary USB access where operationally feasible.
  • Track vendor advisories for backported fixes in supported distributions.

Validation and detection

  • Inventory Linux kernel versions on systems with USB exposure.
  • Confirm vendor packages include the upstream null-check fix.
  • Review kernel changelogs against the referenced stable commits.
  • Check crash telemetry for USB hub or port-state related kernel oops events.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26716 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux83cb2604f641cecadc275ca18adbba4bf262320f, 83cb2604f641cecadc275ca18adbba4bf262320f, 83cb2604f641cecadc275ca18adbba4bf262320funaffected
LinuxLinux6.5, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.