All reports
Low

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

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-53278

Probability of exploitation in the next 30 days: 0.14%

FIRST EPSS · 2026-11-20

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.

A flaw was found in the Linux kernel's arm_mpam component. This vulnerability occurs when the __destroy_component_cfg() function is called from mpam_disable() before the configuration array has been properly allocated. This can lead to a null pointer dereference, potentially causing a system crash and resulting in a Denial of Service (DoS).