CVE-2022-49674
published 2025-02-26CVE-2022-49674: In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using…
PriorityP431high7.1CVSS 3.1
AVLACLPRLUINSUCHINAH
EPSS
0.29%
21.4th percentile
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix accesses beyond end of raid member array
On dm-raid table load (using raid_ctr), dm-raid allocates an array
rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks
is defined by the number of raid metadata and image tupples passed
into the target's constructor.
In the case of RAID layout changes being requested, that number can be
different from the current number of members for existing raid sets as
defined in their superblocks. Example RAID layout changes include:
- raid1 legs being added/removed
- raid4/5/6/10 number of stripes changed (stripe reshaping)
- takeover to higher raid level (e.g. raid5 -> raid6)
When accessing array members, rs->raid_disks must be used in control
loops instead of the potentially larger value in rs->md.raid_disks.
Otherwise it will cause memory access beyond the end of the rs->devs
array.
Fix this by changing code that is prone to out-of-bounds access.
Also fix validate_raid_redundancy() to validate all devices that are
added. Also, use braces to help clean up raid_iterate_devices().
The out-of-bounds memory accesses was discovered using KASAN.
This commit was verified to pass all LVM2 RAID tests (with KASAN
enabled).
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.14-1 (bookworm) | linux 5.18.14-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < 5e161a8826b63c0b8b43e4a7fad1f956780f42ab | 5e161a8826b63c0b8b43e4a7fad1f956780f42ab |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 | df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < 90de15357504c8097ab29769dc6852e16281e9e8 | 90de15357504c8097ab29769dc6852e16281e9e8 |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < 9bf2b0757b04c78dc5d6e3a198acca98457b32a1 | 9bf2b0757b04c78dc5d6e3a198acca98457b32a1 |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < 6352b2f4d8e95ec0ae576d7705435d64cfa29503 | 6352b2f4d8e95ec0ae576d7705435d64cfa29503 |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 | bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 |
| linux | linux | >= 33e53f06850f44ec9722e08a993ecf8816e447a5 < 332bd0778775d0cf105c4b9e03e460b590749916 | 332bd0778775d0cf105c4b9e03e460b590749916 |
| linux | linux_kernel | < 4.14.287 | 4.14.287 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.136-1 | 5.10.136-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 4.15 < 4.19.251 | 4.19.251 |
| linux | linux_kernel | >= 4.20 < 5.4.204 | 5.4.204 |
| linux | linux_kernel | >= 5.11 < 5.15.53 | 5.15.53 |
| linux | linux_kernel | >= 5.16 < 5.18.10 | 5.18.10 |
| linux | linux_kernel | >= 5.5 < 5.10.129 | 5.10.129 |
CVSS provenance
nvdv3.17.1HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
osv7.1HIGH
vendor_debian7.1HIGH
vendor_redhat7.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-7522-w99f-pjfx: In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix accesses beyond end of raid member array
On dm-raid table load (usi
ghsa_unreviewed·2025-10-24
CVE-2022-49674 [HIGH] CWE-125 GHSA-7522-w99f-pjfx: In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix accesses beyond end of raid member array
On dm-raid table load (usi
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix accesses beyond end of raid member array
On dm-raid table load (using raid_ctr), dm-raid allocates an array
rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks
is defined by the number of raid metadata and image tupples passed
into the target's constructor.
In the case of RAID layout changes being requested, that number can be
different from the current number of members for existing raid sets as
defined in their superblocks. Example RAID layout changes include:
- raid1 legs being added/removed
- raid4/5/6/10 number of stripes changed (stripe reshaping)
- takeover to higher raid level (e.g. raid5 -> raid6)
When accessing array members, rs->raid_disks must be used in control
loops instead o
OSV
CVE-2022-49674: In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using
osv·2025-02-26·CVSS 7.1
CVE-2022-49674 [HIGH] CVE-2022-49674: In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being requested, that number can be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed - raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 -> raid6) When accessing array members, rs->raid_disks must be used in control loops instead of th
Red Hat
kernel: Linux kernel: Device Mapper RAID out-of-bounds access
vendor_redhat·2025-02-26·CVSS 7.1
CVE-2022-49674 [HIGH] CWE-805 kernel: Linux kernel: Device Mapper RAID out-of-bounds access
kernel: Linux kernel: Device Mapper RAID out-of-bounds access
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix accesses beyond end of raid member array
On dm-raid table load (using raid_ctr), dm-raid allocates an array
rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks
is defined by the number of raid metadata and image tupples passed
into the target's constructor.
In the case of RAID layout changes being requested, that number can be
different from the current number of members for existing raid sets as
defined in their superblocks. Example RAID layout changes include:
- raid1 legs being added/removed
- raid4/5/6/10 number of stripes changed (stripe reshaping)
- takeover to higher raid level (e.g. raid5 -> raid6)
When accessing array memb
Debian
CVE-2022-49674: linux - In the Linux kernel, the following vulnerability has been resolved: dm raid: fi...
vendor_debian·2022·CVSS 7.1
CVE-2022-49674 [HIGH] CVE-2022-49674: linux - In the Linux kernel, the following vulnerability has been resolved: dm raid: fi...
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix accesses beyond end of raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being requested, that number can be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed - raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 -> raid6) When accessing array members, rs->raid_disks must be used in control loops instead of th
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/332bd0778775d0cf105c4b9e03e460b590749916https://git.kernel.org/stable/c/5e161a8826b63c0b8b43e4a7fad1f956780f42abhttps://git.kernel.org/stable/c/6352b2f4d8e95ec0ae576d7705435d64cfa29503https://git.kernel.org/stable/c/90de15357504c8097ab29769dc6852e16281e9e8https://git.kernel.org/stable/c/9bf2b0757b04c78dc5d6e3a198acca98457b32a1https://git.kernel.org/stable/c/bcff98500ea3b4e7615ec31d2bdd326bc1ef5134https://git.kernel.org/stable/c/df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85
2025-02-26
Published