CVE-2022-50084 Details
Description
In the Linux kernel, the following vulnerability has been resolved: dm raid: fix address sanitizer warning in raid_status There is this warning when using a kernel with the address sanitizer and running this testsuite: https://gitlab.com/cki-project/kernel-tests/-/tree/main/storage/swraid/scsi_raid ================================================================== BUG: KASAN: slab-out-of-bounds in raid_status+0x1747/0x2820 [dm_raid] Read of size 4 at addr ffff888079d2c7e8 by task lvcreate/13319 CPU: 0 PID: 13319 Comm: lvcreate Not tainted 5.18.0-0.rc3.<snip> #1 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: <TASK> dump_stack_lvl+0x6a/0x9c print_address_description.constprop.0+0x1f/0x1e0 print_report.cold+0x55/0x244 kasan_report+0xc9/0x100 raid_status+0x1747/0x2820 [dm_raid] dm_ima_measure_on_table_load+0x4b8/0xca0 [dm_mod] table_load+0x35c/0x630 [dm_mod] ctl_ioctl+0x411/0x630 [dm_mod] dm_ctl_ioctl+0xa/0x10 [dm_mod] __x64_sys_ioctl+0x12a/0x1a0 do_syscall_64+0x5b/0x80 The warning is caused by reading conf->max_nr_stripes in raid_status. The code in raid_status reads mddev->private, casts it to struct r5conf and reads the entry max_nr_stripes. However, if we have different raid type than 4/5/6, mddev->private doesn't point to struct r5conf; it may point to struct r0conf, struct r1conf, struct r10conf or struct mpconf. If we cast a pointer to one of these structs to struct r5conf, we will be reading invalid memory and KASAN warns about it. Fix this bug by reading struct r5conf only if raid type is 4, 5 or 6.
A vulnerability in the Linux kernel's dm raid component has been identified, which causes a slab-out-of-bounds error. This issue arises when the kernel is compiled with the address sanitizer enabled and the dm raid status function is called. The problem occurs because the raid_status function incorrectly assumes that the private data of the mddev structure always points to a r5conf structure, which is only true for certain RAID types. As a result, the function may read invalid memory, triggering a warning from the address sanitizer.
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/1ae0ebfb576b72c2ef400917a5484ebe7892d80b | kernel.org | Patch |
| https://git.kernel.org/stable/c/1fbeea217d8f297fe0e0956a1516d14ba97d0396 | kernel.org | Patch |
| https://git.kernel.org/stable/c/49dba30638e091120256a9e89125340795f034dc | kernel.org | Patch |
| https://git.kernel.org/stable/c/4c233811a49578634d10a5e70a9dfa569d451e94 | kernel.org | Patch |
| https://git.kernel.org/stable/c/90b006da40dd42285b24dd3c940d2c32aca9a70b | kernel.org | Patch |
| https://git.kernel.org/stable/c/b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abe | kernel.org | Patch |
| https://git.kernel.org/stable/c/b856ce5f4b55f752144baf17e9d5c415072652c5 | kernel.org | Patch |
| https://git.kernel.org/stable/c/cb583ca6125ac64c98e9d65128e95ebb5be7d322 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d8971b595d7adac3421c21f59918241f1574061e | 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.9.326 >= 4.10, < 4.14.291 >= 4.15, < 4.19.256 >= 4.20, < 5.4.211 >= 5.5, < 5.10.137 >= 5.11, < 5.15.61 >= 5.16, < 5.18.18 >= 5.19, < 5.19.2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 18, 2025 | Initial Analysis | [email protected] |
| Jun 18, 2025 | New CVE Received | kernel.org |