CVE-2026-31768

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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

A fix is available — apply it.

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

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read()

Add a DMA-safe buffer and use it for spi_read() instead of a stack memory. All SPI buffers must be DMA-safe.

Since we only need up to 3 bytes, we just use a u8[] instead of __be16 and __be32 and change the conversion functions appropriately.

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

May 1, 2026

Last Modified

September 8, 2026

Advisory Details (6)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

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

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

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

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

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

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/768461517a28d80fe81ea4d5d03a90cd184ea6ad
generic

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67b3a91bdc48220bfb67155ab528121b9c822782
generic

iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/014c6d27878d3883f7bb065610768fd021de1a96

Vendor Advisories for CVE-2026-31768(1)

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

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-08ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-08ubuntu
linuxKernel @ 6.1.168—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 ... 7.2~rc5-1~exp1 (496 versions)——
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 (125 versions)6.19.12-1—

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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 233 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31768?
CVE-2026-31768 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: iio: adc: ti-adc161s626: use DMA-safe memory for spi_read() Add a DMA-safe buffer and use it for spi_read() instead of a stack memory. All SPI buffers must be DMA-safe. Since we only need up to 3 bytes, we just use a u8[] instead…
When was CVE-2026-31768 disclosed?
CVE-2026-31768 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31768 actively exploited?
CVE-2026-31768 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31768?
CVE-2026-31768 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31768?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31768, 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-31768

Explore →

Is Your Infrastructure Affected by CVE-2026-31768?

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

Start Free Scan →Browse All CVEs