CVE-2026-93070

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. 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 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:

media: ipu6: Do not free aux device pdata after init

ipu6_bus_initialize_device() stores the isys/psys pdata pointer in struct ipu6_bus_device and initializes the auxiliary device. After that point, error unwinding must drop the auxiliary device reference and let ipu6_bus_release() free both the bus device and adev->pdata.

The isys and psys init paths already call put_device() when MMU initialization fails, and ipu6_bus_add_device() calls auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths therefore run the bus release callback. The extra kfree(pdata) in the callers can release the same object a second time.

Remove the manual pdata frees after the auxiliary device has been initialized.

This issue was found by a static analysis checker and confirmed by manual source review.

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
6th
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 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

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

media: ipu6: Do not free aux device pdata after init - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: ipu6: Do not free aux device pdata after init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9be07216af4cfc4813e1a46ce26407d31ea845de
generic

media: ipu6: Do not free aux device pdata after init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d102d1f0631807a491a140f67c9628dea85dfd2
generic

media: ipu6: Do not free aux device pdata after init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5323ed5a7bb2568191ec676b2035b0396105aa05

Vendor Advisories for CVE-2026-93070(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 23× in last 7d / 66× 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 04:27 UTCEG score recompute
  2. 2026-10-05 04:27 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 15:20 UTCGHSA enrichment
  5. 2026-10-04 02:10 UTCEG score recompute
  6. 2026-10-04 02:10 UTCGHSA enrichment
  7. 2026-10-03 13:04 UTCGHSA enrichment
  8. 2026-10-02 23:58 UTCEG score recompute
  9. 2026-10-02 23:58 UTCGHSA enrichment
  10. 2026-10-02 10:50 UTCGHSA enrichment
  11. 2026-10-01 21:30 UTCEG score recompute
  12. 2026-10-01 21:30 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 08:24 UTCGHSA enrichment
  15. 2026-09-30 19:18 UTCEG score recompute
  16. 2026-09-30 19:18 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 06:12 UTCGHSA enrichment
  19. 2026-09-29 17:06 UTCEG score recompute
  20. 2026-09-29 17:05 UTCGHSA enrichment
  21. 2026-09-29 03:59 UTCEG score recompute
  22. 2026-09-29 03:59 UTCGHSA enrichment
  23. 2026-09-28 14:51 UTCGHSA enrichment
  24. 2026-09-28 01:45 UTCEG score recompute
  25. 2026-09-28 01:45 UTCGHSA enrichment
Show 41 more
  1. 2026-09-27 13:49 UTCEPSS rescore
  2. 2026-09-27 12:36 UTCGHSA enrichment
  3. 2026-09-26 23:29 UTCEG score recompute
  4. 2026-09-26 23:29 UTCGHSA enrichment
  5. 2026-09-26 15:59 UTCEPSS rescore
  6. 2026-09-26 10:04 UTCEG score recompute
  7. 2026-09-26 10:04 UTCGHSA enrichment
  8. 2026-09-25 20:54 UTCGHSA enrichment
  9. 2026-09-25 07:48 UTCGHSA enrichment
  10. 2026-09-24 18:42 UTCEG score recompute
  11. 2026-09-24 18:42 UTCGHSA enrichment
  12. 2026-09-24 14:04 UTCEPSS rescore
  13. 2026-09-24 05:36 UTCEG score recompute
  14. 2026-09-24 05:36 UTCGHSA enrichment
  15. 2026-09-23 17:54 UTCEPSS rescore
  16. 2026-09-23 16:30 UTCGHSA enrichment
  17. 2026-09-23 03:24 UTCEG score recompute
  18. 2026-09-23 03:24 UTCGHSA enrichment
  19. 2026-09-22 16:01 UTCEPSS rescore
  20. 2026-09-22 14:18 UTCGHSA enrichment
  21. 2026-09-22 01:11 UTCEG score recompute
  22. 2026-09-22 01:11 UTCGHSA enrichment
  23. 2026-09-21 21:09 UTCEPSS rescore
  24. 2026-09-21 12:05 UTCGHSA enrichment
  25. 2026-09-20 22:59 UTCEG score recompute
  26. 2026-09-20 22:58 UTCGHSA enrichment
  27. 2026-09-20 20:16 UTCEPSS rescore
  28. 2026-09-20 09:50 UTCGHSA enrichment
  29. 2026-09-19 20:43 UTCEG score recompute
  30. 2026-09-19 20:43 UTCGHSA enrichment
  31. 2026-09-19 07:37 UTCEG score recompute
  32. 2026-09-19 07:37 UTCGHSA enrichment
  33. 2026-09-18 19:28 UTCEPSS rescore
  34. 2026-09-18 18:29 UTCEG score recompute
  35. 2026-09-18 18:29 UTCGHSA enrichment
  36. 2026-09-18 18:00 UTCEG score recompute▲ 7.80
  37. 2026-09-18 18:00 UTCGHSA enrichment
  38. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  39. 2026-09-17 17:24 UTCNVD update
  40. 2026-09-17 16:22 UTCEG score recompute
  41. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93070?
CVE-2026-93070 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: media: ipu6: Do not free aux device pdata after init ipu6businitialize_device() stores the isys/psys pdata pointer in struct ipu6busdevice and initializes the auxiliary device. After that point, error unwinding must drop the…
When was CVE-2026-93070 disclosed?
CVE-2026-93070 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93070 actively exploited?
CVE-2026-93070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93070?
CVE-2026-93070 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-93070?
No fix for CVE-2026-93070 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-93070 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-93070

Explore →

Is Your Infrastructure Affected by CVE-2026-93070?

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

Book a Demo →Browse All CVEs