CVE-2026-31729

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

usb: typec: ucsi: validate connector number in ucsi_notify_common()

The connector number extracted from CCI via UCSI_CCI_CONNECTOR() is a 7-bit field (0-127) that is used to index into the connector array in ucsi_connector_change(). However, the array is only allocated for the number of connectors reported by the device (typically 2-4 entries).

A malicious or malfunctioning device could report an out-of-range connector number in the CCI, causing an out-of-bounds array access in ucsi_connector_change().

Add a bounds check in ucsi_notify_common(), the central point where CCI is parsed after arriving from hardware, so that bogus connector numbers are rejected before they propagate further.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (4)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

usb: typec: ucsi: validate connector number in ucsi_notify_common() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f6dcbf2b024d55549959402f1db6c614e51d52cb
generic

usb: typec: ucsi: validate connector number in ucsi_notify_common() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f4e608fe12b7ac6a4a57176ab0296bb5a110a078
generic

usb: typec: ucsi: validate connector number in ucsi_notify_common() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2d8c17ac01a1b1f638ea5d340a884ccc5015186
generic

usb: typec: ucsi: validate connector number in ucsi_notify_common() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98429e9ec89a5e3a204112dfaa2dbe6ca28493a0

Vendor Advisories for CVE-2026-31729(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.81osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 8× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 220 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-04 00:59 UTCOSV refresh
  3. 2026-09-02 14:11 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 14:17 UTCEPSS rescore
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 13:44 UTCEG score recompute
  22. 2026-08-17 13:44 UTCVendor advisory
  23. 2026-08-17 13:44 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 05:18 UTCEG score recompute
Show 75 more
  1. 2026-08-16 05:18 UTCVendor advisory
  2. 2026-08-16 05:18 UTCGHSA enrichment
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 16:44 UTCVendor advisory
  6. 2026-08-14 16:44 UTCGHSA enrichment
  7. 2026-08-14 03:47 UTCEG score recompute
  8. 2026-08-14 03:47 UTCVendor advisory
  9. 2026-08-14 03:47 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 06:42 UTCVendor advisory
  12. 2026-08-13 06:42 UTCGHSA enrichment
  13. 2026-08-12 17:25 UTCEG score recompute
  14. 2026-08-12 17:25 UTCVendor advisory
  15. 2026-08-12 17:25 UTCGHSA enrichment
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 16:22 UTCEG score recompute
  18. 2026-08-11 16:22 UTCVendor advisory
  19. 2026-08-11 16:22 UTCGHSA enrichment
  20. 2026-08-11 01:49 UTCEG score recompute
  21. 2026-08-11 01:49 UTCVendor advisory
  22. 2026-08-11 01:49 UTCGHSA enrichment
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 04:31 UTCVendor advisory
  25. 2026-08-10 04:31 UTCGHSA enrichment
  26. 2026-08-09 15:44 UTCEG score recompute
  27. 2026-08-09 15:44 UTCVendor advisory
  28. 2026-08-09 15:44 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 02:56 UTCEG score recompute
  31. 2026-08-09 02:56 UTCVendor advisory
  32. 2026-08-09 02:56 UTCGHSA enrichment
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 04:10 UTCEG score recompute
  35. 2026-08-08 04:10 UTCVendor advisory
  36. 2026-08-08 04:10 UTCGHSA enrichment
  37. 2026-08-07 15:22 UTCVendor advisory
  38. 2026-08-07 15:22 UTCGHSA enrichment
  39. 2026-08-07 02:34 UTCEG score recompute
  40. 2026-08-07 02:34 UTCVendor advisory
  41. 2026-08-07 02:34 UTCGHSA enrichment
  42. 2026-08-06 13:46 UTCEPSS rescore
  43. 2026-08-06 11:25 UTCVendor advisory
  44. 2026-08-06 11:25 UTCGHSA enrichment
  45. 2026-08-05 22:36 UTCEG score recompute
  46. 2026-08-05 22:36 UTCVendor advisory
  47. 2026-08-05 22:36 UTCGHSA enrichment
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:38 UTCEPSS rescore
  51. 2026-08-03 20:24 UTCEG score recompute
  52. 2026-08-03 20:24 UTCVendor advisory
  53. 2026-08-03 20:24 UTCGHSA enrichment
  54. 2026-08-03 10:36 UTCEPSS rescore
  55. 2026-08-02 18:28 UTCVendor advisory
  56. 2026-08-02 18:28 UTCGHSA enrichment
  57. 2026-08-02 05:40 UTCEG score recompute
  58. 2026-08-02 05:40 UTCVendor advisory
  59. 2026-08-02 05:40 UTCGHSA enrichment
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-28 15:36 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 14:17 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 03:08 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-21 15:24 UTCEPSS rescore
  74. 2026-07-21 15:24 UTCEPSS rescore
  75. 2026-07-20 12:02 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-31729?
CVE-2026-31729 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: validate connector number in ucsinotifycommon() The connector number extracted from CCI via UCSICCICONNECTOR() is a 7-bit field (0-127) that is used to index into the connector array in ucsiconnectorchange().…
When was CVE-2026-31729 disclosed?
CVE-2026-31729 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31729 actively exploited?
CVE-2026-31729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-31729?
CVE-2026-31729 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31729?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31729, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31729

Explore →

Is Your Infrastructure Affected by CVE-2026-31729?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.