CVE-2022-50084— dm raid: fix address sanitizer warning in raid_status
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2022-50084
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
dm raid: fix address sanitizer warning in raid_status
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于dm_raid在raid_status中越界读取导致内存破坏。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2022-50084
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2022-50084
请登录查看更多情报信息。
Same Patch Batch · Linux · 2025-06-18 · 362 CVEs total
| CVE-2022-50104 | powerpc/xive: Fix refcount leak in xive_get_max_prio | |
| CVE-2022-50116 | tty: n_gsm: fix deadlock and link starvation in outgoing data path | |
| CVE-2022-50114 | net: 9p: fix refcount leak in p9_read_work() error handling | |
| CVE-2022-50113 | ASoc: audio-graph-card2: Fix refcount leak bug in __graph_get_type() | |
| CVE-2022-50112 | rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge | |
| CVE-2022-50111 | ASoC: mt6359: Fix refcount leak bug | |
| CVE-2022-50110 | watchdog: sp5100_tco: Fix a memory leak of EFCH MMIO resource | |
| CVE-2022-50109 | video: fbdev: amba-clcd: Fix refcount leak bugs | |
| CVE-2022-50108 | mfd: max77620: Fix refcount leak in max77620_initialise_fps | |
| CVE-2022-50106 | powerpc/cell/axon_msi: Fix refcount leak in setup_msi_msg_address | |
| CVE-2022-50107 | cifs: Fix memory leak when using fscache | |
| CVE-2022-50105 | powerpc/spufs: Fix refcount leak in spufs_init_isolated_loader | |
| CVE-2022-50099 | video: fbdev: arkfb: Check the size of screen before memset_io() | |
| CVE-2022-50095 | posix-cpu-timers: Cleanup CPU timers before freeing them during exec | |
| CVE-2022-50094 | spmi: trace: fix stack-out-of-bound access in SPMI tracing functions | |
| CVE-2022-50096 | x86/kprobes: Update kcb status flag after singlestepping | |
| CVE-2022-50097 | video: fbdev: s3fb: Check the size of screen before memset_io() | |
| CVE-2022-50098 | scsi: qla2xxx: Fix crash due to stale SRB access around I/O timeouts | |
| CVE-2022-50101 | video: fbdev: vt8623fb: Check the size of screen before memset_io() | |
| CVE-2022-50103 | sched, cpuset: Fix dl_cpu_busy() panic due to empty cs->cpus_allowed |
Showing top 20 of 362 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2022-50084
No comments yet