CVE-2026-53278: arm_mpam: Check whether the config array is allocated before destroying it
In the Linux kernel, the following vulnerability has been resolved:
armmpam: 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 destroycomponentcfg() is called from mpamdisable() 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.
destroycomponentcfg() also frees the mbwustate as this is allocated by allocatecomponentcfg(). As the mbwustate is allocated after comp->cfg is set, and is also under mpamlistlock, only the first pointer needs checking.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53278?
CVE-2026-53278 has a risk rating of 27, indicating a moderate severity level.
How do I fix CVE-2026-53278?
To mitigate CVE-2026-53278, update to the latest version of the Linux kernel where the vulnerability has been resolved.
What systems are affected by CVE-2026-53278?
CVE-2026-53278 affects the Linux kernel specifically in versions prior to the fix implemented after June 26, 2026.
What type of vulnerability is CVE-2026-53278?
CVE-2026-53278 is a code execution vulnerability related to memory management in the Linux kernel.
What are the potential impacts of CVE-2026-53278?
If exploited, CVE-2026-53278 could lead to system crashes or unexpected behaviors due to improper memory handling.