arm_mpam: Disable driver unbind to avoid UAF
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel arm_mpam driver can access a freed component after a user unbinds its only remaining MSC and then reads the resctrl schemata file. Triggering this requires local access to the unbind sysfs interface and the schemata file; the input does not specify the privileges required.
Engineers running Linux kernels with the arm_mpam driver should check their kernel vendor’s advisory; affected versions were not specified.