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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
2.9%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 136 total refreshes for this CVE.

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

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 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs