CVE-2026-53067

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc

pci_epf_alloc_doorbell() stores the allocated doorbell message array in epf->db_msg/epf->num_db before requesting MSI vectors. If MSI allocation fails, the array is freed but the EPF state may still point to freed memory.

Clear epf->db_msg and epf->num_db on the MSI allocation failure path so that later cleanup cannot double-free the array and callers can retry allocation.

Also return -EBUSY when doorbells have already been allocated to prevent leaking or overwriting an existing allocation.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

Published

June 24, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Patch available.
generic

PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1cba96c0a795124c3229293ed7b5b5765e66f259
generic

PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/175717cfc06cab79f84cd037d66dda1b8564cd9e

Vendor Advisories for CVE-2026-53067(1)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-23ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-23ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-23ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-23ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-23ubuntu

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

All Vendor Advisories

(10)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53067?
CVE-2026-53067 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI: endpoint: pci-ep-msi: Fix error unwind and prevent double alloc pciepfalloc_doorbell() stores the allocated doorbell message array in epf->dbmsg/epf->numdb before requesting MSI vectors. If MSI allocation fails, the array is…
When was CVE-2026-53067 disclosed?
CVE-2026-53067 was first published on June 24, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53067 actively exploited?
CVE-2026-53067 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-53067?
CVE-2026-53067 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53067?
A fix for CVE-2026-53067 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53067 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-53067

Explore →

Is Your Infrastructure Affected by CVE-2026-53067?

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

Book a Demo →Browse All CVEs