[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061839-CVE-2022-50200-51f0@gregkh>
Date: Wed, 18 Jun 2025 13:04:25 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50200: selinux: Add boundary check in put_entry()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
selinux: Add boundary check in put_entry()
Just like next_entry(), boundary check is necessary to prevent memory
out-of-bound access.
The Linux kernel CVE team has assigned CVE-2022-50200 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.291 with commit 2dabe6a872a5744865372eb30ea51e8ccd21305a
Fixed in 4.19.256 with commit 477722f31ad73aa779154d1d7e00825538389f76
Fixed in 5.4.211 with commit 90bdf50ae70c5571a277b5601e4f5df210831e0a
Fixed in 5.10.137 with commit adbfdaacde18faf6cd4e490764045375266b3fbd
Fixed in 5.15.61 with commit 7363a69d8ca8f0086f8e1196c8ddaf0e168614b1
Fixed in 5.18.18 with commit 9605f50157cae00eb299e1189a6d708c84935ad8
Fixed in 5.19.2 with commit dedd558d9765b72c66e5a53948e9f5abc3ece1f6
Fixed in 6.0 with commit 15ec76fb29be31df2bccb30fc09875274cba2776
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-50200
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/selinux/ss/policydb.h
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/2dabe6a872a5744865372eb30ea51e8ccd21305a
https://git.kernel.org/stable/c/477722f31ad73aa779154d1d7e00825538389f76
https://git.kernel.org/stable/c/90bdf50ae70c5571a277b5601e4f5df210831e0a
https://git.kernel.org/stable/c/adbfdaacde18faf6cd4e490764045375266b3fbd
https://git.kernel.org/stable/c/7363a69d8ca8f0086f8e1196c8ddaf0e168614b1
https://git.kernel.org/stable/c/9605f50157cae00eb299e1189a6d708c84935ad8
https://git.kernel.org/stable/c/dedd558d9765b72c66e5a53948e9f5abc3ece1f6
https://git.kernel.org/stable/c/15ec76fb29be31df2bccb30fc09875274cba2776
Powered by blists - more mailing lists