CVE-2022-50085: dm raid: fix address sanitizer warning in raid_resume
In the Linux kernel, the following vulnerability has been resolved:
dm raid: fix address sanitizer warning in raid_resume
There is a KASAN warning in raid_resume when running the lvm test
lvconvert-raid.sh. The reason for the warning is that mddev->raid_disks
is greater than rs->raid_disks, so the loop touches one entry beyond
the allocated length.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50085 is a Linux kernel dm-raid memory safety bug. During RAID resume handling, the kernel can access one entry beyond an allocated array. The provided sources do not give a CVSS score, business impact, or exploitation evidence, so urgency depends on whether affected Linux kernels and dm-raid/LVM RAID are present.
Executive priority
Treat this as a targeted Linux kernel maintenance item, not an emergency based on current evidence. Prioritize internet-facing or critical infrastructure only if it uses dm-raid on affected kernels. The absence of severity and exploitation data limits business-risk certainty.
Technical view
The flaw is in Linux kernel dm raid raid_resume. A KASAN warning showed mddev->raid_disks can exceed rs->raid_disks, causing a loop to touch one entry beyond the allocated length. The CVE record lists Linux kernel affected versions and multiple upstream stable commit references resolving the issue.
Likely exposure
Exposure is most plausible on Linux systems using device-mapper RAID or LVM RAID paths on affected kernel builds. Systems without dm-raid use are less likely to reach the vulnerable code. Distribution backports may change exposure, so package-level vendor advisories should be checked.
Exploitation context
The supplied sources do not report active exploitation, public weaponization, KEV listing, exploit prerequisites, or a remote attack path. Evidence is limited to a KASAN-discovered out-of-bounds access during lvm testing, so exploitability and impact are not established here.
Researcher notes
Key unknowns are exploitability, privilege requirements, and practical impact. The record describes an out-of-bounds access found by KASAN in raid_resume testing. Analysis should focus on affected kernel lineage, distro backports, dm-raid reachability, and whether the condition can be attacker-influenced.
Mitigation direction
Inventory Linux hosts using dm-raid or LVM RAID.
Check vendor kernel advisories for CVE-2022-50085 fixes.
Prioritize updates to kernels containing referenced stable fixes.
Apply distribution-supported kernel updates during normal maintenance windows.
Monitor vendor guidance for severity or exploitability updates.
Validation and detection
Confirm running kernel versions against vendor CVE data.
Identify systems using device-mapper RAID or LVM RAID.
Verify installed kernel packages include the relevant stable fix.
Review kernel logs for RAID resume or KASAN-related warnings.
Retest affected LVM RAID workflows after updating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50085 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
9Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.