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

> A malicious USB device can trigger uninitialized stack data disclosure in the Linux kernel DisplayPort altmode driver.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** AZL-92783, BELL-CVE-2026-63961, DEBIAN-CVE-2026-63961, GHSA-m857-r6wp-m3gv, ROOT-OS-UBUNTU-2204-CVE-2026-63961, UBUNTU-CVE-2026-63961

## What is CVE-2026-63961?

CVE-2026-63961 is a vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

usb: typec: altmodes/displayport: validate count before reading Status Update VDO

A broken/malicious device can send the incorrect count for a status
update VDO, which will cause the kernel to read uninitialized stack data
and send it off elsewhere.

Fix this up by correctly verifying the count for the update object.

## Which versions are affected by CVE-2026-63961?


## How do I fix CVE-2026-63961?

Apply the vendor's patch.

## Is CVE-2026-63961 being exploited?

There is no known exploitation of CVE-2026-63961 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63961 and fix it if it is affected.

What it is: CVE-2026-63961 is a vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-63961 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63961/ (Markdown: https://insights.sbomify.com/CVE-2026-63961/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63961
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63961
- OSV: https://osv.dev/vulnerability/CVE-2026-63961

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63961/
Summaries are generated and may contain mistakes; the official description above is the record.