VulnerabilityPublished 26 Jun 2026Updated 6 Nov 2026

CVE-2026-53278: Linux kernel · arm_mpam: Check whether the config array is allocated before destroying it

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 8eb6dc76eeae5302c0d885906a0e469ef9630a59 or 6ccbb613b42a1f1ba7bfd547a148f644a902a25c when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in 8eb6dc76eeae5302c0d885906a0e469ef9630a59, 6ccbb613b42a1f1ba7bfd547a148f644a902a25c

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 8eb6dc76eeae5302c0d885906a0e469ef9630a59 or 6ccbb613b42a1f1ba7bfd547a148f644a902a25c.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 3bd04fe7d807bbdcfe75b29ca82fae4e2d7dc524, < 8eb6dc76eeae5302c0d885906a0e469ef9630a59	Fixed in 8eb6dc76eeae5302c0d885906a0e469ef9630a59
LinuxLinux	Affected ≥ 3bd04fe7d807bbdcfe75b29ca82fae4e2d7dc524, < 6ccbb613b42a1f1ba7bfd547a148f644a902a25c	Fixed in 6ccbb613b42a1f1ba7bfd547a148f644a902a25c
LinuxLinux	Affected =6.19	Fixed in–

Description

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.

References

Community reviews

Loading reviews…