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-89471power: supply: cros_usbpd-charger: bound the EC-reported port count

Description

In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd-charger: bound the EC-reported port count cros_usbpd_charger_probe() reads two port counts from the EC and uses one of them, num_charger_ports, as the loop bound when populating a fixed-size array: struct port_data *ports[EC_USB_PD_MAX_PORTS]; /* 8 entries */ ... for (i = 0; i < charger->num_charger_ports; i++) charger->ports[charger->num_registered_psy++] = port; Both num_usbpd_ports (from EC_CMD_USB_PD_PORTS) and num_charger_ports (from EC_CMD_CHARGE_PORT_COUNT) are u8 values reported by the EC. The only validation is a sanity check that compares the two EC-reported values against each other: if (num_charger_ports < num_usbpd_ports || num_charger_ports > num_usbpd_ports + 1) return -EPROTO; It never checks either count against EC_USB_PD_MAX_PORTS, the size of the ports[] array. A malfunctioning, malicious or compromised EC that reports num_usbpd_ports == num_charger_ports == N for any N > 8 (for example both 255) passes this check, and the loop then writes N pointers into the 8-entry ports[] array embedded in the devm_kzalloc()'d charger_data, overflowing it by up to 255 - 8 = 247 entries (~1976 bytes): a slab out-of-bounds write. Reject a port count larger than the ports[] array can hold.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days 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-89471, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 96% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < 0b5096f6804161b61451b1cec0e38678630be849
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < c46c9f447415ca802afab51dea1eafc08ddff1c6
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < a1905375dfc0b9612bbee52fc066e3a70c0d671d
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < 2746d502b12b343384fb747bdef9cbcfbd7444a2
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < fd29d08ee487f3bf50f2575aaa74f78a74b09b21
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < 78be8b7403ff7638162438b664a07d19da76059e
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < 3d1e01443b221081258ff34ea0cdd0431e4ff62e
    • affected f68b883e8fad23ed0ac4756d91594809d78678ed – < 48355ce49359740f52e94d3623f6fc557ce341f0
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .