CVE-2022-49674
dm raid: fix accesses beyond end of raid member array
- Published
- Updated
- Reserved
- Assigned by
- Linux
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).
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.29% · top 78% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Weakness
Affected products
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < 5e161a8826b63c0b8b43e4a7fad1f956780f42ab
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < 90de15357504c8097ab29769dc6852e16281e9e8
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < 9bf2b0757b04c78dc5d6e3a198acca98457b32a1
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < 6352b2f4d8e95ec0ae576d7705435d64cfa29503
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < bcff98500ea3b4e7615ec31d2bdd326bc1ef5134
- affected 33e53f06850f44ec9722e08a993ecf8816e447a5 – < 332bd0778775d0cf105c4b9e03e460b590749916
- affected 4.8
- unaffected < 4.8
- unaffected 4.14.287 – ≤ 4.14.*
- unaffected 4.19.251 – ≤ 4.19.*
- unaffected 5.4.204 – ≤ 5.4.*
- unaffected 5.10.129 – ≤ 5.10.*
- unaffected 5.15.53 – ≤ 5.15.*
- unaffected 5.18.10 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References (7)
- https://git.kernel.org/stable/c/5e161a8826b63c0b8b43e4a7fad1f956780f42ab (opens in a new tab)
- https://git.kernel.org/stable/c/df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 (opens in a new tab)
- https://git.kernel.org/stable/c/90de15357504c8097ab29769dc6852e16281e9e8 (opens in a new tab)
- https://git.kernel.org/stable/c/9bf2b0757b04c78dc5d6e3a198acca98457b32a1 (opens in a new tab)
- https://git.kernel.org/stable/c/6352b2f4d8e95ec0ae576d7705435d64cfa29503 (opens in a new tab)
- https://git.kernel.org/stable/c/bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 (opens in a new tab)
- https://git.kernel.org/stable/c/332bd0778775d0cf105c4b9e03e460b590749916 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49674)Record last updated .