Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53832: md/raid10: fix null-ptr-deref in raid10_sync_request

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.25% (FIRST EPSS).
  • Fixed version: Linux Linux 14964127be77884003976a392c9faa9ebaabbbe1, 38d33593260536840b49fd1dcac9aedfd14a9d42, 68695084077e3de9d3e94e09238ace2b6f246446.

Low priority for now. Upgrade to Linux Linux 14964127be77884003976a392c9faa9ebaabbbe1, 38d33593260536840b49fd1dcac9aedfd14a9d42, 68695084077e3de9d3e94e09238ace2b6f246446 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 null-ptr-deref in raid10_sync_request init_resync() inits mempool and sets conf->have_replacemnt at the beginning of sync, close_sync() frees the mempool when sync is completed. After [1] recovery might be skipped and init_resync() is called but close_sync() is not. null-ptr-deref occurs with r10bio->dev[i].repl_bio. The following is one way to reproduce the issue. 1) create a array, wait for resync to complete, mddev->recovery_cp is set to MaxSector. 2) recovery is woken and it is skipped. conf->have_replacement is set to 0 in init_resync(). close_sync() not called. 3) some io errors and rdev A is set to WantReplacement. 4) a new device is added and set to A's replacement. 5) recovery is woken, A have replacement, but conf->have_replacemnt is 0. r10bio->dev[i].repl_bio will not be alloced and null-ptr-deref occurs. Fix it by not calling init_resync() if recovery skipped. [1] commit 7e83ccbecd60 ("md/raid10: Allow skipping recovery when clean arrays are assembled")

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 17th 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-53832

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.

—

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.10affected
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before 38d33593260536840b49fd1dcac9aedfd14a9d42affected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before 14964127be77884003976a392c9faa9ebaabbbe1affected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before bdbf104b1c91fbf38f82c522ebf75429f094292aaffected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before 68695084077e3de9d3e94e09238ace2b6f246446affected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before b50fd1c3d9d0175aa29ff2706ef36cc178bc356aaffected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before 99b503e4edc5938885d839cf0e7571963f75d800affected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before 9e9efc77efd1956cc244af975240f2513d78a371affected · git
    • 7e83ccbecd608b971f340e951c9e84cd0343002f and later · before a405c6f0229526160aa3f177f65e20c86fce84c5affected · git
    • before 3.10not 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.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1
Red Hat:rhel_eus:8.8::baseosbpftoolbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseosbpftool-debuginfobefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernelbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-abi-stablelistsbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-corebefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debugbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-corebefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-debuginfobefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-develbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modulesbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modules-extrabefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfobefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-develbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-docbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modulesbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modules-extrabefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-toolsbefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-tools-debuginfobefore 0:4.18.0-477.36.1.el8_80:4.18.0-477.36.1.el8_8

+12

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-53830Dec 9, 2025 · platform/x86: think-lmi: Fix memory leak when showing current settings
    0Monitor
  • ← EarlierCVE-2023-53831Dec 9, 2025 · net: read sk->sk_family once in sk_mc_loop()
    0Monitor
  • Later →CVE-2023-53833Dec 9, 2025 · drm/i915: Fix NULL ptr deref by checking new_crtc_state
    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 Linux14964127be77884003976a392c9faa9ebaabbbe1Vendor (CNA)
Linux Linux38d33593260536840b49fd1dcac9aedfd14a9d42Vendor (CNA)
Linux Linux68695084077e3de9d3e94e09238ace2b6f246446Vendor (CNA)
Linux Linux99b503e4edc5938885d839cf0e7571963f75d800Vendor (CNA)
Linux Linux9e9efc77efd1956cc244af975240f2513d78a371Vendor (CNA)
Linux Linuxa405c6f0229526160aa3f177f65e20c86fce84c5Vendor (CNA)
Linux Linuxb50fd1c3d9d0175aa29ff2706ef36cc178bc356aVendor (CNA)
Linux Linuxbdbf104b1c91fbf38f82c522ebf75429f094292aVendor (CNA)
debian:linux6.1.37-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.36.1.el8_8 · Red Hat:rhel_eus:8.8::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.

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

All records