CVE-2026-53278

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

arm_mpam: Check whether the config array is allocated before destroying it

__destroy_component_cfg() is called to free the configuration array. It uses the embedded 'garbage' structure, which means the array has to be allocated.

If __destroy_component_cfg() is called from mpam_disable() before the configuration was ever allocated, then a NULL pointer is dereferenced.

Check for this case and return early if the configuration is not allocated.

__destroy_component_cfg() also frees the mbwu_state as this is allocated by __allocate_component_cfg(). As the mbwu_state is allocated after comp->cfg is set, and is also under mpam_list_lock, only the first pointer needs checking.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 8, 2026

Advisory Details (2)

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

arm_mpam: Check whether the config array is allocated before destroying it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8eb6dc76eeae5302c0d885906a0e469ef9630a59
generic

arm_mpam: Check whether the config array is allocated before destroying it - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ccbb613b42a1f1ba7bfd547a148f644a902a25c

Vendor Advisories for CVE-2026-53278(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-06ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-06ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-06ubuntu

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.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 8× 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.

Showing the most recent 100 of 180 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53278?
CVE-2026-53278 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: arm_mpam: Check whether the config array is allocated before destroying it destroycomponentcfg() is called to free the configuration array. It uses the embedded 'garbage' structure, which means the array has to be allocated. If…
When was CVE-2026-53278 disclosed?
CVE-2026-53278 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-53278 actively exploited?
CVE-2026-53278 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53278?
CVE-2026-53278 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53278?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53278, 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-53278

Explore →

Is Your Infrastructure Affected by CVE-2026-53278?

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

Start Free Scan →Browse All CVEs