cbcvebase.
CVE-2022-50084
published 2025-06-18

CVE-2022-50084: 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…

PriorityP429high7.1CVSS 3.1
AVLACLPRLUINSUCHINAH
EPSS
0.17%
6.5th percentile
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. #1 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: 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.

Affected

23 ranges
VendorProductVersion rangeFixed in
debianlinux< linux 6.0.2-1 (bookworm)linux 6.0.2-1 (bookworm)
linuxlinux——
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < 1ae0ebfb576b72c2ef400917a5484ebe7892d80b1ae0ebfb576b72c2ef400917a5484ebe7892d80b
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < 90b006da40dd42285b24dd3c940d2c32aca9a70b90b006da40dd42285b24dd3c940d2c32aca9a70b
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < b856ce5f4b55f752144baf17e9d5c415072652c5b856ce5f4b55f752144baf17e9d5c415072652c5
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < cb583ca6125ac64c98e9d65128e95ebb5be7d322cb583ca6125ac64c98e9d65128e95ebb5be7d322
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < 49dba30638e091120256a9e89125340795f034dc49dba30638e091120256a9e89125340795f034dc
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < 4c233811a49578634d10a5e70a9dfa569d451e944c233811a49578634d10a5e70a9dfa569d451e94
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < d8971b595d7adac3421c21f59918241f1574061ed8971b595d7adac3421c21f59918241f1574061e
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abeb4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abe
linuxlinux>= 3a1c1ef2fd62087c3d6521de217ddb9360776658 < 1fbeea217d8f297fe0e0956a1516d14ba97d03961fbeea217d8f297fe0e0956a1516d14ba97d0396
linuxlinux_kernel< 4.9.3264.9.326
linuxlinux_kernel>= 0 < 5.10.140-15.10.140-1
linuxlinux_kernel>= 0 < 6.0.2-16.0.2-1
linuxlinux_kernel>= 0 < 6.0.2-16.0.2-1
linuxlinux_kernel>= 0 < 6.0.2-16.0.2-1
linuxlinux_kernel>= 4.10 < 4.14.2914.14.291
linuxlinux_kernel>= 4.15 < 4.19.2564.19.256
linuxlinux_kernel>= 4.20 < 5.4.2115.4.211
linuxlinux_kernel>= 5.11 < 5.15.615.15.61
linuxlinux_kernel>= 5.16 < 5.18.185.18.18
linuxlinux_kernel>= 5.19 < 5.19.25.19.2
linuxlinux_kernel>= 5.5 < 5.10.1375.10.137

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.