Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53722: md: raid1: fix potential OOB in raid1_remove_disk()

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 25a68f2286be56fb3a6f9fa0e269c04b5e6c6e24, 4bdb92eaf645e312975357adc3c4e9523b6e67f1, 4f7d853b4590fc20e90dd50e346c02811a8c5b08.

Low priority for now. Upgrade to Linux Linux 25a68f2286be56fb3a6f9fa0e269c04b5e6c6e24, 4bdb92eaf645e312975357adc3c4e9523b6e67f1, 4f7d853b4590fc20e90dd50e346c02811a8c5b08 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: raid1: fix potential OOB in raid1_remove_disk() If rddev->raid_disk is greater than mddev->raid_disks, there will be an out-of-bounds in raid1_remove_disk(). We have already found similar reports as follows: 1) commit d17f744e883b ("md-raid10: fix KASAN warning") 2) commit 1ebc2cec0b7d ("dm raid: fix KASAN warning in raid5_remove_disk") Fix this bug by checking whether the "number" variable is valid.

—No exploit Fix available
Published
Oct 22, 2025
Updated
Oct 28, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
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-2023-53722

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.

—

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 beedf40f73939f248c81802eda08a2a8148ea13eaffected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 91fbd4e75cb573f44d2619a9dc2f9ba927040760affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 25a68f2286be56fb3a6f9fa0e269c04b5e6c6e24affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 7993cfc041481a3a9cd4a3858088fc846b8ccaf7affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 4f96c0665f9f4cf70130c9757750dc43dc679c82affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 4f7d853b4590fc20e90dd50e346c02811a8c5b08affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 4bdb92eaf645e312975357adc3c4e9523b6e67f1affected · git
    • b8321b68d1445f308324517e45fb0a5c2b48e271 and later · before 8b0472b50bcf0f19a5119b00a53b63579c8e1e4daffected · git
    • before 3.3not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.6-16.5.6-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-docsbefore 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.192.13.0.101-108.192.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.192.13.0.101-108.192.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-53720Oct 22, 2025 · net/mlx5e: Release the label when replacing existing ct entry
    0Monitor
  • ← EarlierCVE-2023-53721Oct 22, 2025 · wifi: ath12k: Fix a NULL pointer dereference in ath12k_mac_op_hw_scan()
    0Monitor
  • Later →CVE-2023-53723Oct 22, 2025 · drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
    0Monitor

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 Linux25a68f2286be56fb3a6f9fa0e269c04b5e6c6e24Vendor (CNA)
Linux Linux4bdb92eaf645e312975357adc3c4e9523b6e67f1Vendor (CNA)
Linux Linux4f7d853b4590fc20e90dd50e346c02811a8c5b08Vendor (CNA)
Linux Linux4f96c0665f9f4cf70130c9757750dc43dc679c82Vendor (CNA)
Linux Linux7993cfc041481a3a9cd4a3858088fc846b8ccaf7Vendor (CNA)
Linux Linux8b0472b50bcf0f19a5119b00a53b63579c8e1e4dVendor (CNA)
Linux Linux91fbd4e75cb573f44d2619a9dc2f9ba927040760Vendor (CNA)
Linux Linuxbeedf40f73939f248c81802eda08a2a8148ea13eVendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)
suse:kernel-default3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-docs3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-source3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.192.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records