CVE-2026-89941

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

iio: buffer: Make IIO DMA fence release RCU-safe

The dma_fence documentation states that if a custom release implementation is provided, the dma_fence object must be freed in an RCU-safe way. The current iio_dma_fence implementation uses kfree(), which might result in a use-after-free.

Remove the custom release implementation. This makes the DMA fence core fall back to dma_fence_free(), which calls kfree_rcu() on the fence. This requires that the fence be the first member of struct iio_dma_fence.

Using the default release method for extended DMA fence structures is a common pattern.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available.
generic

iio: buffer: Make IIO DMA fence release RCU-safe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8662e56c31cf23b61ca3d11b516efb94c35b8026
generic

iio: buffer: Make IIO DMA fence release RCU-safe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/311595dc0b5621f74d8eb4dc38ef4efcdfe7e769
generic

iio: buffer: Make IIO DMA fence release RCU-safe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11cef99491117d4264603df159c4ff5f3845a059
generic

iio: buffer: Make IIO DMA fence release RCU-safe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06a9460b8b792e109cbc934a856d02e5cff217ef

Vendor Advisories for CVE-2026-89941(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 24× in last 7d / 80× 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.

  1. 2026-10-05 09:42 UTCEG score recompute
  2. 2026-10-05 09:42 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 22:17 UTCGHSA enrichment
  5. 2026-10-04 10:51 UTCGHSA enrichment
  6. 2026-10-03 23:22 UTCEG score recompute
  7. 2026-10-03 23:22 UTCGHSA enrichment
  8. 2026-10-03 11:54 UTCGHSA enrichment
  9. 2026-10-02 23:59 UTCEG score recompute
  10. 2026-10-02 23:59 UTCGHSA enrichment
  11. 2026-10-02 12:25 UTCGHSA enrichment
  12. 2026-10-02 00:11 UTCEG score recompute
  13. 2026-10-02 00:11 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 12:04 UTCGHSA enrichment
  16. 2026-10-01 00:39 UTCEG score recompute
  17. 2026-10-01 00:38 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 12:20 UTCGHSA enrichment
  20. 2026-09-30 00:54 UTCEG score recompute
  21. 2026-09-30 00:54 UTCGHSA enrichment
  22. 2026-09-29 12:20 UTCGHSA enrichment
  23. 2026-09-29 00:55 UTCEG score recompute
  24. 2026-09-29 00:55 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 55 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:30 UTCGHSA enrichment
  3. 2026-09-28 02:05 UTCGHSA enrichment
  4. 2026-09-27 14:40 UTCEG score recompute
  5. 2026-09-27 14:40 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 03:14 UTCEG score recompute
  8. 2026-09-27 03:14 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 15:48 UTCGHSA enrichment
  11. 2026-09-26 04:22 UTCEG score recompute
  12. 2026-09-26 04:22 UTCGHSA enrichment
  13. 2026-09-25 16:56 UTCGHSA enrichment
  14. 2026-09-25 05:31 UTCGHSA enrichment
  15. 2026-09-24 18:06 UTCEG score recompute
  16. 2026-09-24 18:06 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 06:38 UTCGHSA enrichment
  19. 2026-09-23 19:14 UTCEG score recompute
  20. 2026-09-23 19:13 UTCGHSA enrichment
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-23 07:21 UTCGHSA enrichment
  23. 2026-09-22 19:56 UTCEG score recompute
  24. 2026-09-22 19:56 UTCGHSA enrichment
  25. 2026-09-22 16:01 UTCEPSS rescore
  26. 2026-09-22 08:30 UTCEG score recompute
  27. 2026-09-22 08:30 UTCGHSA enrichment
  28. 2026-09-21 21:09 UTCEPSS rescore
  29. 2026-09-21 21:04 UTCGHSA enrichment
  30. 2026-09-21 09:39 UTCGHSA enrichment
  31. 2026-09-20 22:14 UTCEG score recompute
  32. 2026-09-20 22:14 UTCGHSA enrichment
  33. 2026-09-20 20:16 UTCEPSS rescore
  34. 2026-09-20 10:48 UTCGHSA enrichment
  35. 2026-09-19 23:23 UTCEG score recompute
  36. 2026-09-19 23:23 UTCGHSA enrichment
  37. 2026-09-19 11:58 UTCGHSA enrichment
  38. 2026-09-19 00:33 UTCEG score recompute
  39. 2026-09-19 00:32 UTCGHSA enrichment
  40. 2026-09-18 19:28 UTCEPSS rescore
  41. 2026-09-18 13:07 UTCGHSA enrichment
  42. 2026-09-18 01:42 UTCEG score recompute
  43. 2026-09-18 01:42 UTCGHSA enrichment
  44. 2026-09-17 19:32 UTCEPSS rescore
  45. 2026-09-17 14:17 UTCGHSA enrichment
  46. 2026-09-17 02:51 UTCEG score recompute
  47. 2026-09-17 02:51 UTCGHSA enrichment
  48. 2026-09-16 15:23 UTCEG score recompute
  49. 2026-09-16 15:23 UTCGHSA enrichment
  50. 2026-09-16 14:47 UTCEG score recompute▲ 7.80
  51. 2026-09-16 14:47 UTCGHSA enrichment
  52. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  53. 2026-09-16 11:21 UTCNVD update
  54. 2026-09-16 10:38 UTCEG score recompute
  55. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89941?
CVE-2026-89941 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: iio: buffer: Make IIO DMA fence release RCU-safe The dma_fence documentation states that if a custom release implementation is provided, the dma_fence object must be freed in an RCU-safe way. The current iiodmafence implementation…
When was CVE-2026-89941 disclosed?
CVE-2026-89941 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89941 actively exploited?
CVE-2026-89941 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89941?
CVE-2026-89941 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89941?
A fix for CVE-2026-89941 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89941 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-89941?

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

Book a Demo →Browse All CVEs