Skip to content
Fencer Vulns
high 7.8

CVE-2026-31729 json

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

published 2026-05-01 6 mo ago modified 2026-11-06 2 d ago also EUVD-2026-26542

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.12.81, 6.18.22, 6.19.12, 7.0
  • linux Debian 13 6.12.85-1
  • linux Debian 14 6.19.12-1

debian advisories DEBIAN-CVE-2026-31729

  • linux Ubuntu 24.04 LTS 6.8.0-136.136
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1061.62
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1063.71
  • linux-gkeop Ubuntu 24.04 LTS 6.8.0-1046.50
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1061.65

ubuntu advisories UBUNTU-CVE-2026-31729

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Linux Micro 6.2 6.12.0-160000.34.1
  • kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.34.1
  • kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.34.1
  • kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.34.1
  • kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.34.1.160000.2.15
  • kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.34.1
  • kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.34.1
  • kernel-obs-qa SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.34.1

suse advisories SUSE-SU-2026:22048-1SUSE-SU-2026:22087-1SUSE-SU-2026:22076-1SUSE-SU-2026:22043-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-31729 updated cvss 5.5

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

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
3 d ago

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-129 Improper Validation of Array Index
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.