# md/raid10: fix wrong setting of max_corr_read_errors

CVE record · `CVE-2023-53313`

- **Identifiers:** `CVE-2023-53313`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 16 Sept 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 16 Sept 2025, 16:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before 74050a3fdd4aecfd2cbf74d3c145812ab2744375` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before 025fde32fb957a5c271711bc66841f817ff5f299` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before 31c805a44b7569ca1017a4714385182d98bba212` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before b1d8f38310bce3282374983b229d94edbaf1e570` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before 3c76920e547d4b931bed758bad83fd658dd88b4e` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before 05d10428e8dffed0bac2502f34151729fc189cd3` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before aef6e98eb772594edd4399625e4e1bbe45971fa1` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before e83cb411aa1c6c9617db9329897f4506ba9e9b9d` (git)
  - affected: `1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d to before f8b20a405428803bd9881881d8242c9d72c6b2b2` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `2.6.33`
  - unaffected: `before 2.6.33` (semver)
  - unaffected: `4.14.322 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.291 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.251 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.188 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.121 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.39 to 6.1.*, inclusive` (semver)
  - unaffected: `6.3.13 to 6.3.*, inclusive` (semver)
  - unaffected: `6.4.4 to 6.4.*, inclusive` (semver)
  - unaffected: `6.5 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0017, the 6th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 16 Sept 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2023-53313](https://www.cve.org/CVERecord?id=CVE-2023-53313)
- [NVD: CVE-2023-53313](https://nvd.nist.gov/vuln/detail/CVE-2023-53313)

### References from the CNA

- <https://git.kernel.org/stable/c/74050a3fdd4aecfd2cbf74d3c145812ab2744375>
- <https://git.kernel.org/stable/c/025fde32fb957a5c271711bc66841f817ff5f299>
- <https://git.kernel.org/stable/c/31c805a44b7569ca1017a4714385182d98bba212>
- <https://git.kernel.org/stable/c/b1d8f38310bce3282374983b229d94edbaf1e570>
- <https://git.kernel.org/stable/c/3c76920e547d4b931bed758bad83fd658dd88b4e>
- <https://git.kernel.org/stable/c/05d10428e8dffed0bac2502f34151729fc189cd3>
- <https://git.kernel.org/stable/c/aef6e98eb772594edd4399625e4e1bbe45971fa1>
- <https://git.kernel.org/stable/c/e83cb411aa1c6c9617db9329897f4506ba9e9b9d>
- <https://git.kernel.org/stable/c/f8b20a405428803bd9881881d8242c9d72c6b2b2>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-53313>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-53313/>. Everything for agents: <https://agentprime.io/llms.txt>.
