LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35790: usb: typec: altmodes/displayport: create sysfs nodes as driver's default device attribute group

In the Linux kernel, the following vulnerability has been resolved: usb: typec: altmodes/displayport: create sysfs nodes as driver's default device attribute group The DisplayPort driver's sysfs nodes may be present to the userspace before typec_altmode_set_drvdata() completes in dp_altmode_probe. This means that a sysfs read can trigger a NULL pointer error by deferencing dp->hpd in hpd_show or dp->lock in pin_assignment_show, as dev_get_drvdata() returns NULL in those cases. Remove manual sysfs node creation in favor of adding attribute group as default for devices bound to the driver. The ATTRIBUTE_GROUPS() macro is not used here otherwise the path to the sysfs nodes is no longer compliant with the ABI.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw in the USB Type-C DisplayPort alternate-mode driver. A timing issue can let userspace read driver sysfs attributes before the driver finished attaching its private data, causing a NULL pointer error. The documented impact is kernel error or crash behavior, not data theft or remote compromise.

Executive priority

Handle through normal kernel patch management, with higher priority for managed endpoints or appliances where local crashes affect availability. There is no supplied evidence of active exploitation, but kernel faults can still create operational disruption.

Technical view

During dp_altmode_probe, DisplayPort sysfs nodes may appear before typec_altmode_set_drvdata() completes. Reads of hpd_show or pin_assignment_show can receive NULL from dev_get_drvdata() and dereference dp->hpd or dp->lock. The fix moves sysfs attribute creation into the driver's default device attribute group while preserving ABI path compatibility.

Likely exposure

Exposure is most relevant to Linux systems running affected kernels with the USB Type-C DisplayPort alternate-mode driver in use. The source bundle does not identify affected distributions beyond Debian LTS advisories, nor does it prove remote reachability.

Exploitation context

The bundle marks KEV as false, and no provided source states active exploitation. The described trigger is a userspace sysfs read during driver probing. Treat this primarily as a local denial-of-service or stability risk unless vendor advisories say otherwise.

Researcher notes

The vulnerable condition is a probe-time ordering race around sysfs node visibility and drvdata initialization. The supplied record lacks CVSS, CWE, distribution-specific fixed versions, and exploitability detail. Validation should focus on kernel lineage and whether downstream vendor patches include the stable commits.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Review Debian LTS advisories if running Debian LTS kernels.
  • Prioritize laptops, workstations, and devices using USB-C DisplayPort alternate mode.
  • Check your distribution security tracker for exact fixed package versions.
  • Avoid direct wrangler-style assumptions; follow kernel or distribution guidance only.

Validation and detection

  • Inventory Linux kernel versions on systems with USB-C DisplayPort capability.
  • Confirm whether the DisplayPort Type-C alternate-mode driver is present and loaded.
  • Verify installed kernel packages include vendor fixes for CVE-2024-35790.
  • Review system logs for NULL pointer errors involving DisplayPort altmode sysfs handlers.
  • Confirm patch status against the referenced kernel stable commits or distro advisories.
Prepared
Confidence
medium
Sources
10

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-35790 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
9Source 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
LinuxLinux0e3bb7d6894d9b6e67d6382bb03a46a1dc989588, 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588, 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588, 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588, 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588, 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588unaffected
LinuxLinux4.19, 0, 5.10.238, 5.15.184, 6.1.140, 6.6.24, 6.7.12, 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.