[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061858-CVE-2022-50085-7e05@gregkh>
Date: Wed, 18 Jun 2025 13:02:30 +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-50085: dm raid: fix address sanitizer warning in raid_resume
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix address sanitizer warning in raid_resume
There is a KASAN warning in raid_resume when running the lvm test
lvconvert-raid.sh. The reason for the warning is that mddev->raid_disks
is greater than rs->raid_disks, so the loop touches one entry beyond
the allocated length.
The Linux kernel CVE team has assigned CVE-2022-50085 to this issue.
Affected and fixed versions
===========================
Fixed in 4.14.291 with commit c2f075e729636a44e98d9722e3852c2fa6fa49b6
Fixed in 4.19.256 with commit 3bfdc95466f5be4d8d95db5a5b470d61641a7c24
Fixed in 5.4.211 with commit 71f601c779b3cc1baf497796f5b922c3fe5d2a1e
Fixed in 5.10.137 with commit c2d47bef93fb74aa97d90f9a40ca657b8f376083
Fixed in 5.15.61 with commit 50235d9a1f1f742619ed9963cb9f240e5b821d46
Fixed in 5.18.18 with commit 74af83732a39ab7d3bc9b49219a535853e25679f
Fixed in 5.19.2 with commit 2a9faa704d83ff0b04387e385efd8ae21cd95af6
Fixed in 6.0 with commit 7dad24db59d2d2803576f2e3645728866a056dab
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-50085
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:
drivers/md/dm-raid.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/c2f075e729636a44e98d9722e3852c2fa6fa49b6
https://git.kernel.org/stable/c/3bfdc95466f5be4d8d95db5a5b470d61641a7c24
https://git.kernel.org/stable/c/71f601c779b3cc1baf497796f5b922c3fe5d2a1e
https://git.kernel.org/stable/c/c2d47bef93fb74aa97d90f9a40ca657b8f376083
https://git.kernel.org/stable/c/50235d9a1f1f742619ed9963cb9f240e5b821d46
https://git.kernel.org/stable/c/74af83732a39ab7d3bc9b49219a535853e25679f
https://git.kernel.org/stable/c/2a9faa704d83ff0b04387e385efd8ae21cd95af6
https://git.kernel.org/stable/c/7dad24db59d2d2803576f2e3645728866a056dab
Powered by blists - more mailing lists