Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63958usb: typec: ucsi: validate connector number in ucsi_connector_change()

Description

In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: validate connector number in ucsi_connector_change() The connector number in a UCSI CCI notification is a 7-bit field supplied by the PPM. ucsi_connector_change() uses it to index the ucsi->connector[] array without checking it against the number of connectors the PPM reported at init time, so a buggy or malicious PPM (EC firmware, or an I2C-attached UCSI controller on the ccg / stm32g0 / glink transports) can drive schedule_work() on memory past the end of the array. Reject connector numbers that are zero or exceed cap.num_connectors before dereferencing the array.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63958, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (22 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < cea949203faef9cb783adc7b978cce056271e057
    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < 156b6f0aec6108909b0c4aedc78865b12766b347
    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < bd24d92af4ae021b6209f28e9a57e1bf2260d4fd
    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < 0edd1e21587b0483c7ceb993b9fb9668bbef7433
    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < 5af2719b460ab904c504fc069d1dd2a3aa2b22b0
    • affected c1b0bc2dabfa884dea49c02adaf3cd6b52b33d2f – < 288a81a8507052bcfbf884d39a463c44c42c5fd9
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63958 badge
[![CVE-2026-63958](https://cveledger.app/badge/CVE-2026-63958.svg)](https://cveledger.app/cve/CVE-2026-63958)

Record last updated .