VulnerabilityPublished 19 Jul 2026

CVE-2026-63961: Linux kernel · usb: typec: altmodes/displayport: validate count before reading Status Update VDO

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:48 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to properly validate the count before reading the Status Update VDO. Users should apply the official kernel updates containing this fix once available. No other mitigation actions are indicated.

Description

A vulnerability in the Linux kernel's USB Type-C DisplayPort alternate mode handling could cause the kernel to read uninitialized stack data due to improper validation of a count value sent by a device. This flaw allows a broken or malicious device to trigger reading of unintended memory contents. The issue has been fixed by adding proper validation of the count before reading the Status Update VDO.

Impact

The vulnerability could lead to leakage of uninitialized stack memory contents when interacting with a malicious or broken USB Type-C device using DisplayPort alternate mode. There is no indication of code execution or privilege escalation. No known exploits in the wild have been reported.

Summary

The Linux kernel contained a vulnerability in the USB Type-C alternate modes DisplayPort code where it did not validate the count field before reading the Status Update VDO. A malicious or faulty device could send an incorrect count, causing the kernel to read uninitialized stack memory and potentially leak sensitive data. The fix involved verifying the count value properly before accessing the update object data to prevent reading uninitialized memory.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 15:48 UTC

Technical details

References

Community reviews

Related threats