dm raid: fix address sanitizer warning in raid_status
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
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.291, 4.19.256, 4.9.326, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 5.4.211
- CVEs
- CVE-2022-50084
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 21:41 UTC · Revision 1
Source evidence
dm raid: fix address sanitizer warning in raid_status
core-osv · Original sourcePublished 18 Jun 2025, 11:02 UTC
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
osv:CVE-2022-50084
Kernel
Fixed versions: 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2
Complete source record
{
"id": "541965b45039e071ef8ed503662b705970a9d951b162c4213a1eee82ab5e7450",
"url": "https://osv.dev/vulnerability/CVE-2022-50084",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "dm raid: fix address sanitizer warning in raid_status",
"summary": "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 ",
"evidence": "osv:CVE-2022-50084",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.9.326",
"evidence": "/affected/1/ranges"
},
{
"value": "4.14.291",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.256",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.211",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.137",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.61",
"evidence": "/affected/1/ranges"
},
{
"value": "5.18.18",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50084",
"aliases": [
"CVE-2022-50084"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3a1c1ef2fd62087c3d6521de217ddb9360776658"
},
{
"fixed": "1ae0ebfb576b72c2ef400917a5484ebe7892d80b"
},
{
"fixed": "90b006da40dd42285b24dd3c940d2c32aca9a70b"
},
{
"fixed": "b856ce5f4b55f752144baf17e9d5c415072652c5"
},
{
"fixed": "cb583ca6125ac64c98e9d65128e95ebb5be7d322"
},
{
"fixed": "49dba30638e091120256a9e89125340795f034dc"
},
{
"fixed": "4c233811a49578634d10a5e70a9dfa569d451e94"
},
{
"fixed": "d8971b595d7adac3421c21f59918241f1574061e"
},
{
"fixed": "b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abe"
},
{
"fixed": "1fbeea217d8f297fe0e0956a1516d14ba97d0396"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50084.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.8.0"
},
{
"fixed": "4.9.326"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.10.0"
},
{
"fixed": "4.14.291"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.256"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.211"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.137"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.61"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.18.18"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.19.0"
},
{
"fixed": "5.19.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50084.json"
}
}
],
"modified": "2026-10-28T02:30:23.960768908Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1ae0ebfb576b72c2ef400917a5484ebe7892d80b",
"https://git.kernel.org/stable/c/1fbeea217d8f297fe0e0956a1516d14ba97d0396",
"https://git.kernel.org/stable/c/49dba30638e091120256a9e89125340795f034dc",
"https://git.kernel.org/stable/c/4c233811a49578634d10a5e70a9dfa569d451e94",
"https://git.kernel.org/stable/c/90b006da40dd42285b24dd3c940d2c32aca9a70b",
"https://git.kernel.org/stable/c/b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abe",
"https://git.kernel.org/stable/c/b856ce5f4b55f752144baf17e9d5c415072652c5",
"https://git.kernel.org/stable/c/cb583ca6125ac64c98e9d65128e95ebb5be7d322",
"https://git.kernel.org/stable/c/d8971b595d7adac3421c21f59918241f1574061e",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50084.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50084",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50084.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50084",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 490335,
"published_at": "2025-06-18T11:02:25.998+00:00"
}