Bug 2493704 (CVE-2026-53278) - CVE-2026-53278 kernel: arm_mpam: Check whether the config array is allocated before destroying it
Summary: CVE-2026-53278 kernel: arm_mpam: Check whether the config array is allocated ...
Keywords:
Status: NEW
Alias: CVE-2026-53278
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-26 21:01 UTC by OSIDB Bzimport
Modified: 2026-06-29 10:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-26 21:01:47 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-06-29 10:52:08 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062611-CVE-2026-53278-ec2a@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.