CVE-2026-89938

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 — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious 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

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

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

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF

The atlas driver requests its hardware data-ready IRQ with devm_request_threaded_irq(); its threaded handler queues an irq_work, atlas_work_handler(), that calls iio_trigger_poll(data->trig).

The IRQ is devm-managed, so free_irq() runs from the devres unwind after atlas_remove() returns without flushing that irq_work. Once a buffer is enabled, conversion-complete IRQs keep firing and queueing it; a pending irq_work can therefore run after the unwind has freed atlas_data/indio_dev and the trigger, when atlas_work_handler() derives the atlas_data pointer via container_of() and dereferences data->trig, a use-after-free.

Call iio_trigger_poll_nested() directly from the threaded handler instead of bouncing through irq_work. free_irq() then drains the threaded handler, closing the window; other iio drivers with a threaded data-ready IRQ do the same (e.g. bmi270).

This issue was found by an in-house static analysis tool.

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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
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).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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 (5)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF - kernel/git/stable/linux.git - Linux kernel stable tree

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

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF - kernel/git/stable/linux.git - Linux kernel stable tree

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

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91e12b0fbd7047d02bf4ef4dbc491b9ef0159250
generic

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30b0d44c978bbc857bd68b71dab371805653de70
generic

iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2071624c3d0f497ca91da78858e6f30d7112fea6

Vendor Advisories for CVE-2026-89938(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 39× in last 7d / 109× 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 109 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89938?
CVE-2026-89938 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: iio: chemical: atlas-sensor: use iiotriggerpoll_nested() to fix remove UAF The atlas driver requests its hardware data-ready IRQ with devmrequestthreadedirq(); its threaded handler queues an irqwork, atlasworkhandler(), that calls…
When was CVE-2026-89938 disclosed?
CVE-2026-89938 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-89938 actively exploited?
CVE-2026-89938 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-89938?
CVE-2026-89938 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-89938?
No fix for CVE-2026-89938 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-89938 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-89938

Explore →

Is Your Infrastructure Affected by CVE-2026-89938?

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

Book a Demo →Browse All CVEs