Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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")

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.27% · top 80% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < 38d33593260536840b49fd1dcac9aedfd14a9d42
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < 14964127be77884003976a392c9faa9ebaabbbe1
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < bdbf104b1c91fbf38f82c522ebf75429f094292a
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < 68695084077e3de9d3e94e09238ace2b6f246446
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < b50fd1c3d9d0175aa29ff2706ef36cc178bc356a
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < 99b503e4edc5938885d839cf0e7571963f75d800
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < 9e9efc77efd1956cc244af975240f2513d78a371
    • affected 7e83ccbecd608b971f340e951c9e84cd0343002f – < a405c6f0229526160aa3f177f65e20c86fce84c5
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 4.19.283 – ≤ 4.19.*
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53832 badge
[![CVE-2023-53832](https://cveledger.app/badge/CVE-2023-53832.svg)](https://cveledger.app/cve/CVE-2023-53832)

Record last updated .