CVE-2026-53278

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

published June 26, 2026

CVSS
—
EPSS
0%
Percentile
3.3
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.00143 · 3.3th percentile
Published
2026-06-26T19:40Z
EPSS history
Timeline
  • 26 JUN 19:40Z
    arm_mpam: Check whether the config array is allocated before destroying it
    cvelistv5