CVE-2022-49674 Details
Description
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).
A vulnerability in the Linux kernel's device-mapper RAID implementation allows for out-of-bounds memory access in RAID device arrays. This issue arises when the dm-raid table is loaded, as the allocation of the device array does not properly account for changes in RAID layout that may differ from the current number of members defined in the superblocks. Such layout changes can include modifications to RAID1 legs or adjustments in RAID4/5/6/10 stripe counts. The vulnerability was identified using the Kernel Address Sanitizer (KASAN), and the subsequent memory access beyond the allocated array was fixed by ensuring that the correct number of RAID disks was used in control loops, validating all added devices, and cleaning up the iteration process over RAID devices.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/332bd0778775d0cf105c4b9e03e460b590749916 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5e161a8826b63c0b8b43e4a7fad1f956780f42ab | kernel.org | Patch |
| https://git.kernel.org/stable/c/6352b2f4d8e95ec0ae576d7705435d64cfa29503 | kernel.org | Patch |
| https://git.kernel.org/stable/c/90de15357504c8097ab29769dc6852e16281e9e8 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9bf2b0757b04c78dc5d6e3a198acca98457b32a1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 | kernel.org | Patch |
| https://git.kernel.org/stable/c/df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 4.14.287 >= 4.15, < 4.19.251 >= 4.20, < 5.4.204 >= 5.5, < 5.10.129 >= 5.11, < 5.15.53 >= 5.16, < 5.18.10 5.19 rc1 5.19 rc2 5.19 rc3 5.19 rc4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 24, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |