CVE-2026-53294

HIGHNVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

mailbox: mailbox-test: don't free the reused channel

The RX channel can be aliased to the TX channel if it has a different MMIO. This special case needs to be handled when freeing the channels otherwise a double-free occurs.

CVSS v3
7.8
EG Score
7.8(high)
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
3.0%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 8, 2026

Advisory Details (8)

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

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

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

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

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

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88ebadbf0deefdaccdab868b44ff70a0a257f473
generic

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82f6dcea46cf5de65c4ba7283f7c7b34de4a324d
generic

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d4f3d0f64f1016cb78b400a70b67df91fac99b5
generic

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c209299b0113e289e238fa5f2e8f00c59f76060
generic

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3afca89fae501dbd7421e1777b5b8f033b1d98d0
generic

mailbox: mailbox-test: don't free the reused channel - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/240c71a2aea36a1a4210f911a1c32ea88777e8e4

Vendor Advisories for CVE-2026-53294(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 64× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:41 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 11:44 UTCGHSA enrichment
  13. 2026-07-15 23:47 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 11:50 UTCGHSA enrichment
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 23:36 UTCGHSA enrichment
  20. 2026-07-14 11:33 UTCGHSA enrichment
  21. 2026-07-13 23:36 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 11:39 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 39 more
  1. 2026-07-12 23:39 UTCGHSA enrichment
  2. 2026-07-12 11:42 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 23:44 UTCGHSA enrichment
  5. 2026-07-11 11:47 UTCGHSA enrichment
  6. 2026-07-10 23:49 UTCGHSA enrichment
  7. 2026-07-10 11:48 UTCGHSA enrichment
  8. 2026-07-09 23:50 UTCGHSA enrichment
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 11:52 UTCGHSA enrichment
  12. 2026-07-08 23:55 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 11:58 UTCEG score recompute 7.80
  16. 2026-07-08 11:58 UTCGHSA enrichment
  17. 2026-07-08 04:32 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 14:05 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 06:31 UTCEPSS rescore
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-02 16:33 UTCGHSA enrichment
  30. 2026-07-01 15:07 UTCEPSS rescore
  31. 2026-06-30 23:22 UTCEPSS rescore
  32. 2026-06-29 19:05 UTCGHSA enrichment
  33. 2026-06-29 14:06 UTCEPSS rescore
  34. 2026-06-29 14:06 UTCEPSS rescore
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 04:56 UTCEPSS rescore
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-26 21:37 UTCEG score recompute
  39. 2026-06-26 21:37 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53294?
CVE-2026-53294 is a high vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: mailbox: mailbox-test: don't free the reused channel The RX channel can be aliased to the TX channel if it has a different MMIO. This special case needs to be handled when freeing the channels otherwise a double-free occurs.
When was CVE-2026-53294 disclosed?
CVE-2026-53294 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53294 actively exploited?
CVE-2026-53294 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53294?
CVE-2026-53294 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53294?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53294, 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-53294

Explore →

Is Your Infrastructure Affected by CVE-2026-53294?

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