Skip to content
Noroxi
CVE-2022-50211· NVD / CVE Program· CNA Linux

md-raid10: fix KASAN warning

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0f4d18cbea4a6e37a05fd8ee2887439f85211110, 5f57843565131bb782388f9d993f9ee8f453dee1, 5fd4ffa2372a41361d2bdd27ea5730e4e673240c.

Low priority for now. Upgrade to Linux Linux 0f4d18cbea4a6e37a05fd8ee2887439f85211110, 5f57843565131bb782388f9d993f9ee8f453dee1, 5fd4ffa2372a41361d2bdd27ea5730e4e673240c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: md-raid10: fix KASAN warning There's a KASAN warning in raid10_remove_disk when running the lvm test lvconvert-raid-reshape.sh. We fix this warning by verifying that the value "number" is valid. BUG: KASAN: slab-out-of-bounds in raid10_remove_disk+0x61/0x2a0 [raid10] Read of size 8 at addr ffff889108f3d300 by task mdX_raid10/124682 CPU: 3 PID: 124682 Comm: mdX_raid10 Not tainted 5.19.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report.cold+0x45/0x57a ? __lock_text_start+0x18/0x18 ? raid10_remove_disk+0x61/0x2a0 [raid10] kasan_report+0xa8/0xe0 ? raid10_remove_disk+0x61/0x2a0 [raid10] raid10_remove_disk+0x61/0x2a0 [raid10] Buffer I/O error on dev dm-76, logical block 15344, async page read ? __mutex_unlock_slowpath.constprop.0+0x1e0/0x1e0 remove_and_add_spares+0x367/0x8a0 [md_mod] ? super_written+0x1c0/0x1c0 [md_mod] ? mutex_trylock+0xac/0x120 ? _raw_spin_lock+0x72/0xc0 ? _raw_spin_lock_bh+0xc0/0xc0 md_check_recovery+0x848/0x960 [md_mod] raid10d+0xcf/0x3360 [raid10] ? sched_clock_cpu+0x185/0x1a0 ? rb_erase+0x4d4/0x620 ? var_wake_function+0xe0/0xe0 ? psi_group_change+0x411/0x500 ? preempt_count_sub+0xf/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? raid10_sync_request+0x36c0/0x36c0 [raid10] ? preempt_count_sub+0xf/0xc0 ? _raw_spin_unlock_irqrestore+0x19/0x40 ? del_timer_sync+0xa9/0x100 ? try_to_del_timer_sync+0xc0/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? _raw_spin_unlock_irq+0x11/0x24 ? __list_del_entry_valid+0x68/0xa0 ? finish_wait+0xa3/0x100 md_thread+0x161/0x260 [md_mod] ? unregister_md_personality+0xa0/0xa0 [md_mod] ? _raw_spin_lock_irqsave+0x78/0xc0 ? prepare_to_wait_event+0x2c0/0x2c0 ? unregister_md_personality+0xa0/0xa0 [md_mod] kthread+0x148/0x180 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK> Allocated by task 124495: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x80/0xa0 setup_conf+0x140/0x5c0 [raid10] raid10_run+0x4cd/0x740 [raid10] md_run+0x6f9/0x1300 [md_mod] raid_ctr+0x2531/0x4ac0 [dm_raid] dm_table_add_target+0x2b0/0x620 [dm_mod] table_load+0x1c8/0x400 [dm_mod] ctl_ioctl+0x29e/0x560 [dm_mod] dm_compat_ctl_ioctl+0x7/0x20 [dm_mod] __do_compat_sys_ioctl+0xfa/0x160 do_syscall_64+0x90/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 L __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Second to last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The buggy address belongs to the object at ffff889108f3d200 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 0 bytes to the right of 256-byte region [ffff889108f3d200, ffff889108f3d300) The buggy address belongs to the physical page: page:000000007ef2a34c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1108f3c head:000000007ef2a34c order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=2) raw: 4000000000010200 0000000000000000 dead000000000001 ffff889100042b40 raw: 0000000000000000 0000000080200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff889108f3d200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff889108f3d280: 00 00 ---truncated---

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-50211

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 4.9.326
  • linux linux kernel4.10 and later · before 4.14.291
  • linux linux kernel4.15 and later · before 4.19.256
  • linux linux kernel4.20 and later · before 5.4.211
  • linux linux kernel5.5 and later · before 5.10.137
  • linux linux kernel5.11 and later · before 5.15.61
  • linux linux kernel5.16 and later · before 5.18.18
  • linux linux kernel5.19 and later · before 5.19.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.3affected
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 75fbd370a2cec9e92f48285bd90735ed0c837f52affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before bcbdc26a44aba488d2f7122f2d66801bccb74733affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 7a6ccc8fa192fd357c2d5d4c6ce67c834a179e23affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before ce839b9331c11780470f3d727b6fe3c2794a4620affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 5fd4ffa2372a41361d2bdd27ea5730e4e673240caffected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 0f4d18cbea4a6e37a05fd8ee2887439f85211110affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before bf30b9ba09b0ac2a10f04dce2b0835ec4d178aa6affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 5f57843565131bb782388f9d993f9ee8f453dee1affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before d17f744e883b2f8d13cca252d71cfe8ace346f7daffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.2-16.0.2-1
Red Hat:rhel_aus:8.2::baseosbpftoolbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseosbpftool-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernelbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-abi-whitelistsbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-corebefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debugbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-corebefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-develbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-modulesbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-modules-extrabefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-develbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-modulesbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-modules-extrabefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-toolsbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-tools-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-tools-libsbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseosperfbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseosperf-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseospython3-perfbefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2
Red Hat:rhel_aus:8.2::baseospython3-perf-debuginfobefore 0:4.18.0-193.168.1.el8_20:4.18.0-193.168.1.el8_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-50209Jun 18, 2025 · meson-mx-socinfo: Fix refcount leak in meson_mx_socinfo_init
    22Monitor
  • ← EarlierCVE-2022-50210Jun 18, 2025 · MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
    22Monitor
  • Later →CVE-2022-50212Jun 18, 2025 · netfilter: nf_tables: do not allow CHAIN_ID to refer to another table
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f4d18cbea4a6e37a05fd8ee2887439f85211110Vendor (CNA)
Linux Linux5f57843565131bb782388f9d993f9ee8f453dee1Vendor (CNA)
Linux Linux5fd4ffa2372a41361d2bdd27ea5730e4e673240cVendor (CNA)
Linux Linux75fbd370a2cec9e92f48285bd90735ed0c837f52Vendor (CNA)
Linux Linux7a6ccc8fa192fd357c2d5d4c6ce67c834a179e23Vendor (CNA)
Linux Linuxbcbdc26a44aba488d2f7122f2d66801bccb74733Vendor (CNA)
Linux Linuxbf30b9ba09b0ac2a10f04dce2b0835ec4d178aa6Vendor (CNA)
Linux Linuxce839b9331c11780470f3d727b6fe3c2794a4620Vendor (CNA)
Linux Linuxd17f744e883b2f8d13cca252d71cfe8ace346f7dVendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-abi-whitelists0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-193.168.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
suse:kernel-64kb5.3.18-150300.59.215.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-default3.0.101-108.189.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-default-base5.3.18-150300.59.215.1.150300.18.128.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-docs3.0.101-108.189.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.189.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP3_Update_601-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3Package registry (OSV)
suse:kernel-obs-build5.3.18-150300.59.215.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150300.59.215.1 · SUSE:Linux Enterprise Server 15 SP3-LTSSPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records