CVE-2026-63961
Published Jul 19, 2026
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.
Is your site exposed to CVE-2026-63961?
Run a free security scan — no signup, results in seconds.
References
Other References
https://git.kernel.org/stable/c/64bd6ccc5799f8473d1f37d4d8f53093dfec5c02
https://git.kernel.org/stable/c/6ffdbcd7a02f3af8fff9b6519830369f574ed44c
https://git.kernel.org/stable/c/70e7045849e954e56dcbf441b6330e66bc996306
https://git.kernel.org/stable/c/74aabe9ea30fdfba924fce9594e6aa69a596a4bb
https://git.kernel.org/stable/c/77a759ec30bc5fb0dd9c867b711d0acfed6c7faa
https://git.kernel.org/stable/c/8a18f896e667df491331371b55d4ad644dc51d60
https://git.kernel.org/stable/c/b10eff5abe6aa2a5af10ed17bddff76e3b6e6b9b
https://git.kernel.org/stable/c/dd7118c010f324497c275e8fd7a35c9baaa2a00f
Frequently Asked Questions
What is CVE-2026-63961? +
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.
How do I check if I'm vulnerable to CVE-2026-63961? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.