Security readout for executives and security teams
Plain-English summary
A Linux ULPI USB driver cleanup error leaves a debugfs directory behind when an interface is removed. That stale directory can block later deferred probes, potentially preventing the affected USB hardware from initializing correctly. The supplied severity is high, although the documented failure is primarily operational availability rather than confirmed data theft or system compromise.
Executive priority
Treat this as a high-rated but hardware-specific kernel issue. Expedite assessment for embedded, appliance, industrial, or USB-dependent systems using ULPI. For systems without relevant hardware or code-path use, handle through the supported kernel patch cycle after confirming vendor exposure. No supplied evidence supports emergency response for active exploitation.
Technical view
The per-device debugfs root uses the ULPI device's parent name, while unregister logic attempted removal using the ULPI device name. This mismatch leaves stale state that can make subsequent deferred probes fail. The kernel fixes align the directory name used during creation and removal. The supplied CVSS is 7.8 local, low-complexity, low-privilege.
Likely exposure
Exposure is most relevant to Linux systems using ULPI-connected USB hardware and exercising interface removal or deferred reprobe paths. The bundle marks versions 5.18, 6.1.79, 6.6.18, 6.7.6, and 6.8 affected; it also contains an anomalous "0" entry. Exact distribution package exposure should be confirmed with vendor advisories or backport records.
Exploitation context
The bundle does not identify public exploitation, and the CVE is not listed as KEV. It describes a local driver-state cleanup flaw causing probe failures. No evidence provided here demonstrates remote reachability, privilege escalation, or confidentiality and integrity impact, despite the supplied CVSS vector assigning high impact across all three categories.
Researcher notes
The source bundle presents uncertainty: its CVSS claims high confidentiality, integrity, and availability impact, while the description documents a stale debugfs directory and failed reprobes. No CWE is assigned, and the affected-version data includes "0." Researchers should rely on the referenced commits and distribution backport evidence when determining practical scope.
Mitigation direction
- Install a vendor-supported kernel containing the applicable stable fix or distribution backport.
- Prioritize systems that use ULPI USB hardware or have experienced deferred probe failures.
- Review vendor guidance before applying kernel changes where package backport status is unclear.
- Use normal change controls and validate USB hardware initialization after updating.
Validation and detection
- Inventory running kernel versions and identify systems using ULPI-connected USB hardware.
- Compare distribution kernel changelogs against the four referenced stable fix commits.
- Check system logs for repeated deferred probe failures involving ULPI devices.
- Confirm affected USB hardware unregisters and reprobes successfully in a controlled environment.
- Verify the running kernel after remediation, not only the installed package version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-26919 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/d31b886ed6a5095214062ee4fb55037eb930adb6CVE reference, Linux
- https://git.kernel.org/stable/c/330d22aba17a4d30a56f007d0f51291d7e00862bCVE reference, Linux
- https://git.kernel.org/stable/c/33713945cc92ea9c4a1a9479d5c1b7acb7fc4df3CVE reference, Linux
- https://git.kernel.org/stable/c/3caf2b2ad7334ef35f55b95f3e1b138c6f77b368CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.