LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35986: phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered

In the Linux kernel, the following vulnerability has been resolved: phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered The power_supply frame-work is not really designed for there to be long living in kernel references to power_supply devices. Specifically unregistering a power_supply while some other code has a reference to it triggers a WARN in power_supply_unregister(): WARN_ON(atomic_dec_return(&psy->use_cnt)); Folllowed by the power_supply still getting removed and the backing data freed anyway, leaving the tusb1210 charger-detect code with a dangling reference, resulting in a crash the next time tusb1210_get_online() is called. Fix this by only holding the reference in tusb1210_get_online() freeing it at the end of the function. Note this still leaves a theoretical race window, but it avoids the issue when manually rmmod-ing the charger chip driver during development.

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

Security readout for executives and security teams

Plain-English summary

A Linux kernel driver can retain a stale reference after a charger power-supply device is removed. A later charger-status check may access freed memory and crash the system. The documented scenario involves unloading a charger driver during development, so exposure depends on specific TI TUSB1210 hardware, driver use, and device-removal behavior.

Executive priority

Prioritize affected embedded or appliance systems where kernel crashes threaten availability. Treat general Linux fleets as lower immediate exposure unless TI TUSB1210 hardware and the relevant driver path are present. Remediate through supported kernel updates, but do not infer widespread compromise from the high score alone.

Technical view

The TI TUSB1210 PHY charger-detection code can hold a power_supply reference beyond the referenced device’s lifetime. Unregistration frees the backing data despite an outstanding-use warning, leaving a dangling reference for tusb1210_get_online(). The published fix obtains and releases the reference within that function, although the source acknowledges a remaining theoretical race window.

Likely exposure

Likely limited to Linux systems using the TI TUSB1210 PHY charger-detection path where the associated power-supply device can be unregistered. The bundle marks Linux versions including 5.18, 6.1.90, 6.6.30, 6.8.9, and 6.9 as affected, but its version data is ambiguous and requires vendor confirmation.

Exploitation context

The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. The documented trigger is manually unloading the charger-chip driver during development. Local access, low privileges, and high attack complexity appear in the supplied CVSS vector, but dependable security impact beyond a crash is not demonstrated.

Researcher notes

This is a dangling-reference condition resembling use-after-free, with a documented crash following power-supply unregistration. The fix narrows reference lifetime but explicitly leaves a theoretical race. The supplied CVSS claims high confidentiality, integrity, and availability impact; however, the narrative substantiates a crash and does not establish data disclosure, code execution, or privilege escalation.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix or documented backport.
  • Consult the Linux distribution or device vendor to resolve the bundle’s ambiguous affected-version data.
  • Avoid unnecessary unloading or unregistration of relevant charger drivers until remediation is confirmed.
  • Apply the appropriate referenced stable commit when maintaining a custom kernel.

Validation and detection

  • Inventory systems using the TI TUSB1210 PHY and charger-detection functionality.
  • Record installed kernel builds and compare them with vendor advisories and backport documentation.
  • Verify whether the appropriate referenced stable commit exists in each deployed kernel source or package.
  • Review kernel logs for power_supply_unregister warnings or crashes involving tusb1210_get_online().
  • After updating, confirm the vendor package includes the fix and monitor for recurring warnings.
Prepared
Confidence
medium
Sources
6

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-35986 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/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.

2CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

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

CVSS vector scores

2 official scores

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
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:H/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
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838, 48969a5623ed918713552e2b4f9d391c89b5e838unaffected
LinuxLinux5.18, 0, 6.1.90, 6.6.30, 6.8.9, 6.9affected
Weakness

CWE details

No CWE listed

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