# wifi: iwlwifi: mvm: fix potential array out of bounds access

CVE record · `CVE-2023-53575`

- **Identifiers:** `CVE-2023-53575`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Oct 2025, 15:17 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: `5c75a208c2449c6ea24f07610cc052f6a352246c to before 133b1cd4d98bb8b272335c8e6b0e0c399c0b2ffa` (git)
  - affected: `5c75a208c2449c6ea24f07610cc052f6a352246c to before 637452360ecde9ac972d19416e9606529576b302` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.2`
  - unaffected: `before 6.2` (semver)
  - unaffected: `6.4.7 to 6.4.*, inclusive` (semver)
  - unaffected: `6.5 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's iwlwifi driver (mvm component) is affected in version 6.2, where a key length check did not account for the WEP key offset, allowing a possible out-of-bounds array access. The source gives few details on what an attacker needs or what they could do. Upgrade to Linux kernel 6.4.7 or later in the 6.4 series, or to 6.5 or later.

Written 16 Nov 2026.

## 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 4 Oct 2025, 15:17 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-53575)
- 4 Oct 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-53575)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/133b1cd4d98bb8b272335c8e6b0e0c399c0b2ffa>
- <https://git.kernel.org/stable/c/637452360ecde9ac972d19416e9606529576b302>

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-53575>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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