mm, slab: clean up slab->obj_exts always
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 |
|
|
6.12.286.14.66.15In the Linux kernel, the following vulnerability has been resolved:
mm, slab: clean up slab->obj_exts always
When memory allocation profiling is disabled at runtime or due to an error, shutdown_mem_profiling() is called: slab->obj_exts which previously allocated remains. It won't be cleared by unaccount_slab() because of mem_alloc_profiling_enabled() not true. It's incorrect, slab->obj_exts should always be cleaned up in unaccount_slab() to avoid following error:
[...]BUG: Bad page state in process... .. [...]page dumped because: page still charged to cgroup
[andriy.shevchenko@linux.intel.com: fold need_slab_obj_ext() into its only user]
From the CVE record · Linux
The Linux kernel can leave slab object extensions uncleared when memory allocation profiling is disabled at runtime or due to an error. This can cause a bad page state error because a page remains charged to a cgroup. The input does not describe an attacker action, access requirements, or user interaction.
Engineers running Linux kernels with memory allocation profiling should check their versions; affected versions are not specified.