LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46674: usb: dwc3: st: fix probed platform device ref count on probe error path

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: st: fix probed platform device ref count on probe error path The probe function never performs any paltform device allocation, thus error path "undo_platform_dev_alloc" is entirely bogus. It drops the reference count from the platform device being probed. If error path is triggered, this will lead to unbalanced device reference counts and premature release of device resources, thus possible use-after-free when releasing remaining devm-managed resources.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux USB controller driver can mishandle a device reference when initialization fails. Resources may be released too early, creating a possible use-after-free that could crash the system or compromise confidentiality and integrity. The issue requires local access and the affected driver and error path to be reachable.

Executive priority

Treat this as a high-priority platform maintenance issue on systems using the relevant USB controller driver. It is not documented as remotely exploitable or actively exploited, so prioritize verified exposed systems and normal emergency kernel-patching procedures rather than organization-wide incident response.

Technical view

The dwc3-st probe error path incorrectly enters undo_platform_dev_alloc even though probe allocated no platform device. This unbalances the probed device’s reference count, allowing premature resource release while devm-managed cleanup continues. The resulting use-after-free is rated CVSS 3.1 7.8: local, low-complexity, low-privilege, no user interaction, with potentially high impact.

Likely exposure

Exposure is limited to Linux systems using the affected dwc3-st USB platform driver where probe initialization can enter the relevant failure path. The bundle identifies Linux releases from 3.18 through listed 6.x boundaries, but its flattened version data does not establish every affected package. Distribution backports may change exposure.

Exploitation context

The CVSS vector describes a local, low-privilege attack path requiring no user interaction. The failure occurs during device probing, so practical reachability depends on driver configuration, hardware, and the ability to trigger a probe error. The CVE is not in KEV, and the supplied sources provide no evidence of active exploitation.

Researcher notes

The vulnerability is a reference-counting defect on a probe failure path, producing a possible use-after-free during remaining managed-resource cleanup. Stable-kernel commits are supplied for multiple branches. Exact triggering prerequisites, affected configurations, exploitability, and corrected distribution package versions are not fully documented in the bundle; validate them against vendor guidance.

Mitigation direction

  • Install a vendor-supported kernel containing the appropriate stable-branch fix.
  • Consult the Linux distribution’s advisory and package changelog for backport status.
  • Prioritize systems loading the dwc3-st driver or using relevant USB controller hardware.
  • Reboot into the corrected kernel after applying the update.

Validation and detection

  • Record the running kernel version and installed package revision.
  • Check whether the dwc3-st driver is configured, present, or loaded.
  • Confirm vendor advisories mark the installed kernel package as corrected.
  • After updating, verify the running kernel changed to the remediated build.
  • Review kernel logs for USB probe failures or memory-safety symptoms.
Prepared
Confidence
medium
Sources
12

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-46674 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
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

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.

1CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-46674Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinuxf83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7, f83fca0707c66e36f14efef7f68702cb12de70b7unaffected
LinuxLinux3.18, 0, 4.19.321, 5.4.283, 5.10.225, 5.15.166, 6.1.108, 6.6.49, 6.10.8, 6.11affected
Weakness

CWE details

No CWE listed

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