apparmor: avoid per-cpu hold underflow in aa_get_buffer
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:
apparmor: avoid per-cpu hold underflow in aa_get_buffer
When aa_get_buffer() pulls from the per-cpu list it unconditionally decrements cache->hold. If hold reaches 0 while count is still non-zero, the unsigned decrement wraps to UINT_MAX. This keeps hold non-zero for a very long time, so aa_put_buffer() never returns buffers to the global list, which can starve other CPUs and force repeated kmalloc(aa_g_path_max) allocations.
Guard the decrement so hold never underflows.
From the CVE record · Linux
In the Linux kernel, AppArmor's aa_get_buffer() can underflow a per-CPU hold counter. This can prevent buffers from returning to the global list, starving other CPUs and causing repeated allocations. The input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running Linux kernels with AppArmor should check their versions; affected versions are not specified.