CVE-2026-63959·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm/tcpci_maxim: validate header NDO against RX_BYTE_CNT A broken/malicious port can transmit a CRC-valid frame whose header advertises up to seven data objects but whose body carries fewer than that. Check for this, and rightfully reject the message, instead of reading from uninitialized stack memory.
- Severity
- medium
- Software
- Kernel
- Fixed in
- 7.0.12
- Published
Affected versions
From: 6.19
Until: 7.0.12
Fixed in: 7.0.12
How to fix this CVE
Update your Linux kernel to version 7.0.12 or later to patch this USB Type-C vulnerability. The fix adds validation to ensure USB Power Delivery messages have consistent header and body data object counts, preventing reads from uninitialized memory. Systems running kernel versions 6.19 through 7.0.11 should prioritize this update.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against 6.19 to 7.0.11 to determine vulnerability status
- Step 2: Verify USB Type-C/TCPM drivers are loaded by running `lsmod | grep typec` to confirm the vulnerable code path is active
- Step 3: Monitor kernel logs with `sudo journalctl -k --grep='usb\|typec' -n 100` for any USB Power Delivery frame validation errors or malformed message warnings
- Step 4: After updating to 7.0.12+, run `uname -r` again to confirm the patched kernel is booted, then verify TCPM module reloaded with `lsmod | grep tcpm`
FAQ
What is CVE-2026-63959?
This vulnerability exists in the Linux kernel's USB Type-C Power Delivery (TCPM) driver, where it fails to validate that the number of data objects advertised in a message header matches the actual data present in the message body. A malicious USB device can exploit this mismatch to trigger reads from uninitialized kernel stack memory.
Is CVE-2026-63959 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available.
What versions of Kernel are affected by CVE-2026-63959?
Linux kernel versions 6.19 through 7.0.11 are affected. The vulnerability is resolved in version 7.0.12 and later.
How do I check if my server is vulnerable to CVE-2026-63959?
Run `uname -r` to display your kernel version. If the output shows version 6.19 or higher but lower than 7.0.12, your system is vulnerable. You can also check `cat /proc/version` for additional kernel build details.
Does Defensia detect CVE-2026-63959?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2026-63959 will appear in your dashboard with remediation steps and prioritization guidance.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0af00f1459f5dd757f0d392f8caa38039561ac62
- https://git.kernel.org/stable/c/8a8cd4790b08c9f79ea2250b3bd933fd79f67e56
- https://git.kernel.org/stable/c/9b496e3371c04f0a03b7faa5d2442536d00e3998
- https://git.kernel.org/stable/c/aa2f716327be1818e1cb156da8a2844804aaec2f
- https://git.kernel.org/stable/c/c4ab8e2d4432abb646c5c0687f8dab173da901f9
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63959. Free for 1 server.
Get started free