Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-63962: usb: typec: tcpm: bound altmode_desc[] per iteration in svdm_consume_modes()

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3389c149c68c3fea61910ad5d34f7bf3bff44e32, 4505f33dab56c274e82f47f94bf60a8cbf8f4b42, 816c6251409db28f1b875988fcbd2ff1764a81f0.

Low priority for now. Upgrade to Linux Linux 3389c149c68c3fea61910ad5d34f7bf3bff44e32, 4505f33dab56c274e82f47f94bf60a8cbf8f4b42, 816c6251409db28f1b875988fcbd2ff1764a81f0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 19, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-63962

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.19affected
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before f6694bac643c7ae25c0634b63e67d573ed31e5b7affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 816c6251409db28f1b875988fcbd2ff1764a81f0affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 845598b154b9a92e9d279fafafa9405c121ae805affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 4505f33dab56c274e82f47f94bf60a8cbf8f4b42affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before cbad85b446c06adbc5e5bed565871bb918ce9d32affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 3389c149c68c3fea61910ad5d34f7bf3bff44e32affected · git
    • before 4.19not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.67.1.el10_26.12.0-211.67.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-63960Jul 19, 2026 · usb: typec: wcove: don't write past struct pd_message in wcove_read_rx_buffer()
    22Monitor
  • ← EarlierCVE-2026-63961Jul 19, 2026 · usb: typec: altmodes/displayport: validate count before reading Status Update VDO
    22Monitor
  • Later →CVE-2026-63963Jul 19, 2026 · usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3389c149c68c3fea61910ad5d34f7bf3bff44e32Vendor (CNA)
Linux Linux4505f33dab56c274e82f47f94bf60a8cbf8f4b42Vendor (CNA)
Linux Linux816c6251409db28f1b875988fcbd2ff1764a81f0Vendor (CNA)
Linux Linux845598b154b9a92e9d279fafafa9405c121ae805Vendor (CNA)
Linux Linuxcbad85b446c06adbc5e5bed565871bb918ce9d32Vendor (CNA)
Linux Linuxf6694bac643c7ae25c0634b63e67d573ed31e5b7Vendor (CNA)
almalinux:kernel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.67.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.192-1 · Debian:12Package registry (OSV)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.67.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+14

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. CVSS— → 5.5
  2. Severity— → medium
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records