Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-63962

medium

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() svdm_consume…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes() svdm_consume_modes() checks pmdata->altmodes against the array size once before the loop over the count, but forgot to check the bound at every point in the loop. In the well-behaved SVDM discovery flow this is harmless because each of at most SVID_DISCOVERY_MAX SVIDs contributes at most MODE_DISCOVERY_MAX modes, exactly filling altmode_desc[ALTMODE_DISCOVERY_MAX]. But the CMDT_RSP_ACK handler in tcpm_pd_svdm() does not correlate an incoming ACK with any request the port actually sent. Once port->partner is set, an unsolicited Discover Modes ACK is consumed unconditionally. A broken or malicious port partner can therefore drive altmodes to ALTMODE_DISCOVERY_MAX - 1 via the normal flow, and then send one extra Discover Modes ACK with seven VDOs. Because the pre-loop check passes, the loop could then writes up to five entries past altmode_desc[]. For mode_data_prime the next field in struct tcpm_port is the partner_altmode[] pointer array, which then receives partner-chosen SVID/VDO bytes. Move the bound check inside the loop so the array can never be indexed past ALTMODE_DISCOVERY_MAX regardless of how many VDOs the partner supplies or how the function was reached.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-07-19 16:17
Modified: 2026-10-30 17:34
NVD status: Analyzed
Last synced 3 days ago
Verified against the source API 2026-10-30 17:47 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥4.19 <6.1.191, ≥6.2 <6.6.160, ≥6.7 <6.12.93, ≥6.13 <6.18.35, ≥6.19 <7.0.12, 7.1

Weakness classification (CWE)

NVD-CWE-noinfo

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/3389c149c68c3fea61910ad5d34f7bf3bff44e32
Patch / mitigation: https://git.kernel.org/stable/c/4505f33dab56c274e82f47f94bf60a8cbf8f4b42
Patch / mitigation: https://git.kernel.org/stable/c/816c6251409db28f1b875988fcbd2ff1764a81f0
Patch / mitigation: https://git.kernel.org/stable/c/845598b154b9a92e9d279fafafa9405c121ae805
Patch / mitigation: https://git.kernel.org/stable/c/cbad85b446c06adbc5e5bed565871bb918ce9d32
Patch / mitigation: https://git.kernel.org/stable/c/f6694bac643c7ae25c0634b63e67d573ed31e5b7

References

Data sources

NVD CVE API 2.0 — fetched 2026-10-30 17:47 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs