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-31487spi: use generic driver_override infrastructure

Description

In the Linux kernel, the following vulnerability has been resolved: spi: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1] Also note that we do not enable the driver_override feature of struct bus_type, as SPI - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n".

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 7 months 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-31487, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.12% · top 98% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 5039563e7c25eccd7fec1de6706011009d1c5665 – < 6e8eb467bed6aa1a563dba8f366c9fd76ba0004e
    • affected 5039563e7c25eccd7fec1de6706011009d1c5665 – < eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0
    • affected 5039563e7c25eccd7fec1de6706011009d1c5665 – < c73a58661a760373d08a6883af4f0bb5cc991a67
    • affected 5039563e7c25eccd7fec1de6706011009d1c5665 – < e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0
    • affected 5039563e7c25eccd7fec1de6706011009d1c5665 – < cc34d77dd48708d810c12bfd6f5bf03304f6c824
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .