CVE-2022-50860
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.
Affected versions
Linux kernel versions
4.13
and later are affected. Fixed in
5.10.163,
5.15.86,
6.0.16,
6.1.2,
6.2
and their respective stable series.
References
The following references provide additional information about CVE-2022-50860 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/0250cf8d37bb5201a117177afd24dc73a1c81657
-
PatchKernel patch commithttps://git.kernel.org/stable/c/12695b4b76d437b9c0182a6f7dfb2248013a9daf
-
PatchKernel patch commithttps://git.kernel.org/stable/c/5f509fa740b17307f0cba412485072f632d5af36
Frequently asked questions
-
What is CVE-2022-50860?
CVE-2022-50860 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.13 onward and has been patched in 5.10.163, 5.15.86, 6.0.16 and others. CVE-2022-50860 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2022-50860?
Yes — CVE-2022-50860 has been patched. Fixed versions include 5.10.163, 5.15.86, 6.0.16 and others. If you are running Linux kernel 4.13 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-50860 actively exploited?
No — CVE-2022-50860 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.