linux-cve-announce - CVE-2022-50860: apparmor: Fix memleak in alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025123047-CVE-2022-50860-9d3a@gregkh>
Date: Tue, 30 Dec 2025 13:19:56 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50860: apparmor: Fix memleak in alloc_ns()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

apparmor: Fix memleak in alloc_ns()

After changes in commit a1bd627b46d1 ("apparmor: share profile name on
replacement"), the hname member of struct aa_policy is not valid slab
object, but a subset of that, it can not be freed by kfree_sensitive(),
use aa_policy_destroy() to fix it.

The Linux kernel CVE team has assigned CVE-2022-50860 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.13 with commit a1bd627b46d169268a0ee5960899fb5be960a317 and fixed in 5.10.163 with commit 9a32aa87a25d800b2c6f47bc2749a7bfd9a486f3
	Issue introduced in 4.13 with commit a1bd627b46d169268a0ee5960899fb5be960a317 and fixed in 5.15.86 with commit 5f509fa740b17307f0cba412485072f632d5af36
	Issue introduced in 4.13 with commit a1bd627b46d169268a0ee5960899fb5be960a317 and fixed in 6.0.16 with commit 0250cf8d37bb5201a117177afd24dc73a1c81657
	Issue introduced in 4.13 with commit a1bd627b46d169268a0ee5960899fb5be960a317 and fixed in 6.1.2 with commit 12695b4b76d437b9c0182a6f7dfb2248013a9daf
	Issue introduced in 4.13 with commit a1bd627b46d169268a0ee5960899fb5be960a317 and fixed in 6.2 with commit e9e6fa49dbab6d84c676666f3fe7d360497fd65b

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50860
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	security/apparmor/policy_ns.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/9a32aa87a25d800b2c6f47bc2749a7bfd9a486f3
	https://git.kernel.org/stable/c/5f509fa740b17307f0cba412485072f632d5af36
	https://git.kernel.org/stable/c/0250cf8d37bb5201a117177afd24dc73a1c81657
	https://git.kernel.org/stable/c/12695b4b76d437b9c0182a6f7dfb2248013a9daf
	https://git.kernel.org/stable/c/e9e6fa49dbab6d84c676666f3fe7d360497fd65b