CVE-2026-31485

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

spi: spi-fsl-lpspi: fix teardown order issue (UAF)

There is a teardown order issue in the driver. The SPI controller is registered using devm_spi_register_controller(), which delays unregistration of the SPI controller until after the fsl_lpspi_remove() function returns.

As the fsl_lpspi_remove() function synchronously tears down the DMA channels, a running SPI transfer triggers the following NULL pointer dereference due to use after free:

| fsl_lpspi 42550000.spi: I/O Error in DMA RX | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [...] | Call trace: | fsl_lpspi_dma_transfer+0x260/0x340 [spi_fsl_lpspi] | fsl_lpspi_transfer_one+0x198/0x448 [spi_fsl_lpspi] | spi_transfer_one_message+0x49c/0x7c8 | __spi_pump_transfer_message+0x120/0x420 | __spi_sync+0x2c4/0x520 | spi_sync+0x34/0x60 | spidev_message+0x20c/0x378 [spidev] | spidev_ioctl+0x398/0x750 [spidev] [...]

Switch from devm_spi_register_controller() to spi_register_controller() in fsl_lpspi_probe() and add the corresponding spi_unregister_controller() in fsl_lpspi_remove().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 14, 2026

Advisory Details (8)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbe6f40caeebb0b1ea9dfedc259124c1d3cda7a6
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e89e2b97253c124d37bf88e96e5e8ce5c3aeeec3
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3fd54f8b0317fbccc103961ddd660f2a32dcf0b
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5d01f24bc6fbde40b4e567ef9160194b61267bc
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ca4483f36ac1b62e69f8b182c5b8f059e0abecfb
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b341c1176f2e001b3adf0b47154fc31589f7410e
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/adb25339b66112393fd6892ceff926765feb5b86
generic

spi: spi-fsl-lpspi: fix teardown order issue (UAF) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15650dfbaeeb14bcaaf053b93cf631db8d465300

Vendor Advisories for CVE-2026-31485(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)6.19.11-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(23)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 257 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-02 03:04 UTCOSV refresh
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-09-01 04:39 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 14:17 UTCEPSS rescore
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 06:00 UTCEG score recompute
  22. 2026-08-16 06:00 UTCVendor advisory
  23. 2026-08-16 06:00 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 02:10 UTCEG score recompute
Show 75 more
  1. 2026-08-15 02:10 UTCVendor advisory
  2. 2026-08-15 02:10 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 15:15 UTCVendor advisory
  5. 2026-08-14 15:15 UTCGHSA enrichment
  6. 2026-08-14 04:19 UTCEG score recompute
  7. 2026-08-14 04:19 UTCVendor advisory
  8. 2026-08-14 04:19 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 08:39 UTCVendor advisory
  11. 2026-08-13 08:39 UTCGHSA enrichment
  12. 2026-08-12 18:31 UTCEG score recompute
  13. 2026-08-12 18:31 UTCVendor advisory
  14. 2026-08-12 18:31 UTCGHSA enrichment
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 16:47 UTCEG score recompute
  17. 2026-08-11 16:47 UTCVendor advisory
  18. 2026-08-11 16:47 UTCGHSA enrichment
  19. 2026-08-11 02:21 UTCEG score recompute
  20. 2026-08-11 02:21 UTCVendor advisory
  21. 2026-08-11 02:21 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 12:48 UTCVendor advisory
  24. 2026-08-10 12:48 UTCGHSA enrichment
  25. 2026-08-10 01:30 UTCVendor advisory
  26. 2026-08-10 01:30 UTCGHSA enrichment
  27. 2026-08-09 14:34 UTCEG score recompute
  28. 2026-08-09 14:34 UTCVendor advisory
  29. 2026-08-09 14:34 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 03:33 UTCEG score recompute
  32. 2026-08-09 03:33 UTCVendor advisory
  33. 2026-08-09 03:33 UTCGHSA enrichment
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 11:13 UTCVendor advisory
  36. 2026-08-08 11:13 UTCGHSA enrichment
  37. 2026-08-07 23:45 UTCVendor advisory
  38. 2026-08-07 23:45 UTCGHSA enrichment
  39. 2026-08-07 12:49 UTCVendor advisory
  40. 2026-08-07 12:49 UTCGHSA enrichment
  41. 2026-08-06 21:16 UTCEG score recompute
  42. 2026-08-06 21:16 UTCVendor advisory
  43. 2026-08-06 21:16 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-06 10:21 UTCVendor advisory
  46. 2026-08-06 10:21 UTCGHSA enrichment
  47. 2026-08-05 23:05 UTCEG score recompute
  48. 2026-08-05 23:05 UTCVendor advisory
  49. 2026-08-05 23:05 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 15:10 UTCEPSS rescore
  52. 2026-08-04 10:38 UTCEPSS rescore
  53. 2026-08-03 21:14 UTCEG score recompute
  54. 2026-08-03 21:14 UTCVendor advisory
  55. 2026-08-03 21:14 UTCGHSA enrichment
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 23:25 UTCVendor advisory
  58. 2026-08-02 23:25 UTCGHSA enrichment
  59. 2026-08-02 12:28 UTCEG score recompute
  60. 2026-08-02 12:28 UTCVendor advisory
  61. 2026-08-02 12:28 UTCGHSA enrichment
  62. 2026-08-02 02:27 UTCEPSS rescore
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-30 16:27 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-26 14:54 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-25 14:17 UTCEPSS rescore
  71. 2026-07-24 14:17 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 14:18 UTCEPSS rescore
  74. 2026-07-23 03:08 UTCEG score recompute
  75. 2026-07-22 14:08 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31485?
CVE-2026-31485 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: spi-fsl-lpspi: fix teardown order issue (UAF) There is a teardown order issue in the driver. The SPI controller is registered using devmspiregister_controller(), which delays unregistration of the SPI controller until after…
When was CVE-2026-31485 disclosed?
CVE-2026-31485 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31485 actively exploited?
CVE-2026-31485 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-31485?
CVE-2026-31485 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31485?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31485, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31485

Explore →

Is Your Infrastructure Affected by CVE-2026-31485?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs