CVE-2022-49674

Advisory lineage Upstream: 0 Downstream: 13
Analyzed
Published: 26 Feb 2025, 02:24
Last modified:11 May 2026, 19:04

Vulnerability Summary

Overall Risk (default)
medium
28/100
CVSS Score
7.1 HIGH
v3.1 (nvd)
EPSS Score
<0.01% LOW
0% probability -0.01%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

26 Feb 2025, 02:24
Published
Vulnerability first disclosed
11 May 2026, 19:04
Last Modified
Vulnerability information updated

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).

CVSS Metrics

  • v3.1HIGHScore: 7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

EPSS Trends

Current EPSS score: 0.01% Percentile: 0%

Techniques & Countermeasures

  • CWE-125Out-of-bounds Read

    The product reads data past the end, or before the beginning, of the intended buffer.

Affected Systems

  • linuxlinux

    ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < 5e161a8826b63c0b8b43e4a7fad1f956780f42ab | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85 | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < 90de15357504c8097ab29769dc6852e16281e9e8 | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < 9bf2b0757b04c78dc5d6e3a198acca98457b32a1 | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < 6352b2f4d8e95ec0ae576d7705435d64cfa29503 | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < bcff98500ea3b4e7615ec31d2bdd326bc1ef5134 | ≥ 33e53f06850f44ec9722e08a993ecf8816e447a5, < 332bd0778775d0cf105c4b9e03e460b590749916 | 4.8

  • linuxlinux_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

References (7)