apparmor: Fix double free of ns_name in aa_replace_profiles()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 145a0ef21c8e944957f58e2c8ffcd8a10f46266a · < 7998ab3010d2317643f91828f1853d954ef31387| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
apparmor: Fix double free of ns_name in aa_replace_profiles()
if ns_name is NULL after 1071 error = aa_unpack(udata, &lh, &ns_name);
and if ent->ns_name contains an ns_name in 1089 } else if (ent->ns_name) {
then ns_name is assigned the ent->ns_name 1095 ns_name = ent->ns_name;
however ent->ns_name is freed at 1262 aa_load_ent_free(ent);
and then again when freeing ns_name at 1270 kfree(ns_name);
Fix this by NULLing out ent->ns_name after it is transferred to ns_name
From the CVE record · Linux
The Linux kernel’s AppArmor aa_replace_profiles() function can free a namespace name twice when ownership is transferred from a load entry. The input does not specify what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with AppArmor should check their installations; affected versions are not specified.