CVE-2026-64447

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

staging: media: ipu7: fix double-free and use-after-free in error paths

In both ipu7_isys_init() and ipu7_psys_init(), pdata is allocated and then passed to ipu7_bus_initialize_device(), which stores it in adev->pdata. The ipu7_bus_release() function frees adev->pdata when the device's reference count drops to zero.

Two error paths incorrectly call kfree(pdata) after the device teardown has already freed it:

  • When ipu7_mmu_init() fails: put_device() is called, which drops the
reference count to zero and triggers ipu7_bus_release() -> kfree(pdata). The subsequent kfree(pdata) is a double-free.
  • When ipu7_bus_add_device() fails: it calls auxiliary_device_uninit()
internally, which calls put_device() -> ipu7_bus_release() -> kfree(pdata). The subsequent kfree(pdata) is again a double-free.

Note that the kfree(pdata) when ipu7_bus_initialize_device() itself fails is correct, because in that case auxiliary_device_init() failed and the release function was never set up, so pdata must be freed manually.

Additionally, the error code was not saved before calling put_device(), causing ERR_CAST() to dereference the already-freed adev pointer when constructing the return value. Fix this by saving the error from dev_err_probe() before put_device() and returning ERR_PTR() instead.

Remove the redundant kfree(pdata) calls and fix the use-after-free in the return values of the two affected error paths.

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

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

staging: media: ipu7: fix double-free and use-after-free in error paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: media: ipu7: fix double-free and use-after-free in error paths - kernel/git/stable/linux.git - Linux kernel stable tree

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

staging: media: ipu7: fix double-free and use-after-free in error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/837c1f9655421055f751ed34745e820a54a27642

Vendor Advisories for CVE-2026-64447(1)

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

Patch Availability(5)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Weakness Classification(1)

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

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 28× in last 7d / 104× 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 215 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64447?
CVE-2026-64447 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: staging: media: ipu7: fix double-free and use-after-free in error paths In both ipu7isysinit() and ipu7psysinit(), pdata is allocated and then passed to ipu7businitialize_device(), which stores it in adev->pdata. The…
When was CVE-2026-64447 disclosed?
CVE-2026-64447 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64447 actively exploited?
CVE-2026-64447 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 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64447?
CVE-2026-64447 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64447, 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-64447

Explore →

Is Your Infrastructure Affected by CVE-2026-64447?

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