Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64330: usb: typec: tcpm: Validate SVID index in svdm_consume_modes()

Noroxi assessment

Priority: Monitor (action score 31/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.12% (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 012406f89abc52d1d5f07aa5653b519ebf6d2407, 313ca06e7e224ca1dfadd5722fe71fb8bc276b8b, 3e1b1ac47e8163627f159f30d80d51b914620dd4.

Low priority for now. Upgrade to Linux Linux 012406f89abc52d1d5f07aa5653b519ebf6d2407, 313ca06e7e224ca1dfadd5722fe71fb8bc276b8b, 3e1b1ac47e8163627f159f30d80d51b914620dd4 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: Validate SVID index in svdm_consume_modes() In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid = pmdata->svids[pmdata->svid_index]; If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular: - At index 16, it reads the altmodes count. - At index 18 and beyond, it reads into altmode_desc[], which contains partner-supplied SVDM Discovery Modes VDOs. By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode(). Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Sep 4, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 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-64330

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19 and later · before 5.10.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4
  • linux linux kernel7.2

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 89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before d638ec188e95fe60f4b01106ffd41958f8fb3c2caffected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before f8163c414de8640f2ca82ce4dc93409d4cdc2fadaffected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 012406f89abc52d1d5f07aa5653b519ebf6d2407affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before c6d2af3b217a525741c472f0ab45d7d274b8468faffected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 3e1b1ac47e8163627f159f30d80d51b914620dd4affected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 313ca06e7e224ca1dfadd5722fe71fb8bc276b8baffected · git
    • 4ab8c18d4d67321cc7b660559de17511d4fc0237 and later · before 7b681dd5fbf60b24a13c14661e5b7735759fb491affected · git
    • before 4.19not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Same product

linux: all records

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-64328Jul 25, 2026 · usb: gadget: f_fs: Fix DMA fence leak
    22Monitor
  • ← EarlierCVE-2026-64329Jul 25, 2026 · usb: typec: ucsi: ccg: Fix use-after-free of ucsi on remove
    31Monitor
  • Later →CVE-2026-64331Jul 25, 2026 · usbip: vudc: fix NULL deref in vep_dequeue()
    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 Linux012406f89abc52d1d5f07aa5653b519ebf6d2407Vendor (CNA)
Linux Linux313ca06e7e224ca1dfadd5722fe71fb8bc276b8bVendor (CNA)
Linux Linux3e1b1ac47e8163627f159f30d80d51b914620dd4Vendor (CNA)
Linux Linux7b681dd5fbf60b24a13c14661e5b7735759fb491Vendor (CNA)
Linux Linux89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53Vendor (CNA)
Linux Linuxc6d2af3b217a525741c472f0ab45d7d274b8468fVendor (CNA)
Linux Linuxd638ec188e95fe60f4b01106ffd41958f8fb3c2cVendor (CNA)
Linux Linuxf8163c414de8640f2ca82ce4dc93409d4cdc2fadVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

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).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-640186 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access
    37Monitor
  • CVE-2026-4311080 days apartwifi: brcmfmac: validate bsscfg indices in IF events
    35Monitor
  • CVE-2026-4317280 days apartwifi: iwlwifi: fix 22000 series SMEM parsing
    35Monitor
  • CVE-2026-23246129 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration
    35Monitor
  • CVE-2026-642710 days apartInput: touchwin - reset the packet index on every complete packet
    31Monitor
  • CVE-2026-642720 days apartInput: mms114 - fix touch indexing for MMS134S and MMS136
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-129 · Improper Validation of Array Index

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records