arm_mpam: Disable driver unbind to avoid UAF
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: arm_mpam: Disable driver unbind to avoid UAF When a user unbinds an MSC and that MSC is the only MSC left for a component then the corresponding mpam_component will be freed. If the user then goes on to read the schemata file in the resctrl filesystem then the mpam_component will be accessed from resctrl_arch_get_config() leading to a use after free. As the MPAM driver is not a module the unbind sysfs interface is the only way to trigger the remove. Instead of dealing with the complexity of allowing some unused MSC to unbind just remove the unbind sysfs interface.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From f04046f2577a5c76167333ca99d3903ee5331ba0 · fixed in 7d199b6a0651abad3ca6d0877dbedbe8fe6ea9e2; From f04046f2577a5c76167333ca99d3903ee5331ba0 · fixed in bb1a0f582d519c0461b0940116e2b52c5ba31459
- Linux Linux
6.19
- KernelLinux
From 6.19.0 · fixed in 7.2.6