CVE-2026-64447

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 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

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

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

July 27, 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.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 05:26 UTCEG score recompute
  3. 2026-07-27 05:26 UTCGHSA enrichment
  4. 2026-07-27 05:13 UTCEG score recompute 7.80
  5. 2026-07-27 05:13 UTCGHSA enrichment
  6. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 02:47 UTCEG score recompute
  10. 2026-07-26 02:47 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 10:39 UTCNVD update
  14. 2026-07-25 09:26 UTCEG score recompute
  15. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

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 July 27, 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

Explore the affected products and dependency analysis for 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.