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-81017platform/chrome: sensorhub: Bound the EC-reported sensor number

Description

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Bound the EC-reported sensor number Each EC FIFO event carries an 8-bit sensor number (in->sensor_num). cros_ec_sensorhub_ring_handler() validates the FIFO event count, the per-read count and the ring bound, but not the sensor number, which cros_ec_sensor_ring_process_event() then uses unchecked to index sensorhub->batch_state[] - allocated with only sensorhub->sensor_num entries. A sensor number of sensor_num or larger is an out-of-bounds read and write of batch_state[]. Validate the sensor number in the ring handler, where each event is read from the EC, and drop a malformed event before it is used.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    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-81017, 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.18% · top 92% of all CVEs (16 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 145d59baff5944b71551ac518d7fd7d377a9c820 – < 3a76b87e1d065183e2e7ae5b800cb1f6e84f543d
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 2b602ecf6193ecb9720c78b6728d7e09370b1ff1
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 324880f94ba3c6269a607e04f78a4dd4a66b3f53
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < d1b4add68dabfdd6481a4fa198bf3b473d2634d7
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 3d2636dce0a8fe9eecad29010699847be425dc80
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 5eaf7faa99578ae090030d1e2e6ea3b37a615496
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 4d9bf63ed74f859c6698bc01d8fb216ef9253867
    • affected 145d59baff5944b71551ac518d7fd7d377a9c820 – < 833740a2333c2e4db4e02e3d0ffba04e8718a5f3
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • 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-81017 badge
[![CVE-2026-81017](https://cveledger.app/badge/CVE-2026-81017.svg)](https://cveledger.app/cve/CVE-2026-81017)

Record last updated .