Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49674: dm raid: fix accesses beyond end of raid member array

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.28% (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 332bd0778775d0cf105c4b9e03e460b590749916, 5e161a8826b63c0b8b43e4a7fad1f956780f42ab, 6352b2f4d8e95ec0ae576d7705435d64cfa29503.

Low priority for now. Upgrade to Linux Linux 332bd0778775d0cf105c4b9e03e460b590749916, 5e161a8826b63c0b8b43e4a7fad1f956780f42ab, 6352b2f4d8e95ec0ae576d7705435d64cfa29503 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 accesses beyond end of raid member array On dm-raid table load (using raid_ctr), dm-raid allocates an array rs->devs[rs->raid_disks] for the raid device members. rs->raid_disks is defined by the number of raid metadata and image tupples passed into the target's constructor. In the case of RAID layout changes being requested, that number can be different from the current number of members for existing raid sets as defined in their superblocks. Example RAID layout changes include: - raid1 legs being added/removed - raid4/5/6/10 number of stripes changed (stripe reshaping) - takeover to higher raid level (e.g. raid5 -> raid6) When accessing array members, rs->raid_disks must be used in control loops instead of the potentially larger value in rs->md.raid_disks. Otherwise it will cause memory access beyond the end of the rs->devs array. Fix this by changing code that is prone to out-of-bounds access. Also fix validate_raid_redundancy() to validate all devices that are added. Also, use braces to help clean up raid_iterate_devices(). The out-of-bounds memory accesses was discovered using KASAN. This commit was verified to pass all LVM2 RAID tests (with KASAN enabled).

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

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.14.287
  • linux linux kernel4.15 and later · before 4.19.251
  • linux linux kernel4.20 and later · before 5.4.204
  • linux linux kernel5.5 and later · before 5.10.129
  • linux linux kernel5.11 and later · before 5.15.53
  • linux linux kernel5.16 and later · before 5.18.10
  • linux linux kernel5.19

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
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before 5e161a8826b63c0b8b43e4a7fad1f956780f42abaffected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before df1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85affected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before 90de15357504c8097ab29769dc6852e16281e9e8affected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before 9bf2b0757b04c78dc5d6e3a198acca98457b32a1affected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before 6352b2f4d8e95ec0ae576d7705435d64cfa29503affected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before bcff98500ea3b4e7615ec31d2bdd326bc1ef5134affected · git
    • 33e53f06850f44ec9722e08a993ecf8816e447a5 and later · before 332bd0778775d0cf105c4b9e03e460b590749916affected · git
    • before 4.8not affected · semver
    • 4.14.287 and later · up to and including 4.14.*not affected · semver

Package-level exposure

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

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

+58

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-49672Feb 26, 2025 · net: tun: unlink NAPI from device on destruction
    22Monitor
  • ← EarlierCVE-2022-49673Feb 26, 2025 · dm raid: fix KASAN warning in raid5_add_disks
    22Monitor
  • Later →CVE-2022-49675Feb 26, 2025 · tick/nohz: unexport __init-annotated tick_nohz_full_setup()
    22Monitor

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 Linux332bd0778775d0cf105c4b9e03e460b590749916Vendor (CNA)
Linux Linux5e161a8826b63c0b8b43e4a7fad1f956780f42abVendor (CNA)
Linux Linux6352b2f4d8e95ec0ae576d7705435d64cfa29503Vendor (CNA)
Linux Linux90de15357504c8097ab29769dc6852e16281e9e8Vendor (CNA)
Linux Linux9bf2b0757b04c78dc5d6e3a198acca98457b32a1Vendor (CNA)
Linux Linuxbcff98500ea3b4e7615ec31d2bdd326bc1ef5134Vendor (CNA)
Linux Linuxdf1a5ab0dd0775f2ea101c71f2addbc4c0ea0f85Vendor (CNA)
debian:linux5.18.14-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-abi-whitelists0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-193.193.1.el8_2 · Red Hat:rhel_aus:8.2::baseosPackage 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 (6 more)

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

All records