Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50084: dm raid: fix address sanitizer warning in raid_status

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.20% (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 1ae0ebfb576b72c2ef400917a5484ebe7892d80b, 1fbeea217d8f297fe0e0956a1516d14ba97d0396, 49dba30638e091120256a9e89125340795f034dc.

Low priority for now. Upgrade to Linux Linux 1ae0ebfb576b72c2ef400917a5484ebe7892d80b, 1fbeea217d8f297fe0e0956a1516d14ba97d0396, 49dba30638e091120256a9e89125340795f034dc 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: 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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 10th 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-50084

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 4.8affected
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before 1ae0ebfb576b72c2ef400917a5484ebe7892d80baffected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before 90b006da40dd42285b24dd3c940d2c32aca9a70baffected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before b856ce5f4b55f752144baf17e9d5c415072652c5affected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before cb583ca6125ac64c98e9d65128e95ebb5be7d322affected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before 49dba30638e091120256a9e89125340795f034dcaffected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before 4c233811a49578634d10a5e70a9dfa569d451e94affected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before d8971b595d7adac3421c21f59918241f1574061eaffected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before b4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abeaffected · git
    • 3a1c1ef2fd62087c3d6521de217ddb9360776658 and later · before 1fbeea217d8f297fe0e0956a1516d14ba97d0396affected · 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

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2022-50078Jun 18, 2025 · tracing/eprobes: Do not allow eprobes to use $stack, or % for regs
    22Monitor
  • ← EarlierCVE-2022-50079Jun 18, 2025 · drm/amd/display: Check correct bounds for stream encoder instances for DCN303
    28Monitor
  • Later →CVE-2022-50085Jun 18, 2025 · dm raid: fix address sanitizer warning in raid_resume
    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 Linux1ae0ebfb576b72c2ef400917a5484ebe7892d80bVendor (CNA)
Linux Linux1fbeea217d8f297fe0e0956a1516d14ba97d0396Vendor (CNA)
Linux Linux49dba30638e091120256a9e89125340795f034dcVendor (CNA)
Linux Linux4c233811a49578634d10a5e70a9dfa569d451e94Vendor (CNA)
Linux Linux90b006da40dd42285b24dd3c940d2c32aca9a70bVendor (CNA)
Linux Linuxb4c6c07c92b6cba2bf3cb2dfa722debeaf8a8abeVendor (CNA)
Linux Linuxb856ce5f4b55f752144baf17e9d5c415072652c5Vendor (CNA)
Linux Linuxcb583ca6125ac64c98e9d65128e95ebb5be7d322Vendor (CNA)
Linux Linuxd8971b595d7adac3421c21f59918241f1574061eVendor (CNA)
debian:linux6.0.2-1 · Debian:12Package registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

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.

Credits

All researchers

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records