# CVE-2026-53182: wifi: nl80211: reject oversized EMA RNR lists

> An integer overflow in the Linux kernel Wi-Fi driver allows attackers to cause memory corruption or denial of service via oversized RNR lists.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-90905, BELL-CVE-2026-53182, DEBIAN-CVE-2026-53182, GHSA-q6qm-26ch-2w94, ROOT-OS-DEBIAN-12-CVE-2026-53182, ROOT-OS-UBUNTU-2404-CVE-2026-53182, UBUNTU-CVE-2026-53182

## What is CVE-2026-53182?

CVE-2026-53182 is a high-severity vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: nl80211: reject oversized EMA RNR lists

nl80211_parse_rnr_elems() stores the parsed element count in a
u8-backed cfg80211_rnr_elems::cnt field and uses that count to size
the flexible array allocation.

Reject nested NL80211_ATTR_EMA_RNR_ELEMS input once the count reaches
255, before incrementing it again. This keeps the parser aligned with
the data structure it fills and matches the existing bound check used
by nl80211_parse_mbssid_elems().

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-53182?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53182?

Apply the vendor's patch.

## Is CVE-2026-53182 being exploited?

There is no known exploitation of CVE-2026-53182 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53182 and fix it if it is affected.

What it is: CVE-2026-53182 is a high-severity vulnerability in Linux kernel, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53182 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53182/ (Markdown: https://insights.sbomify.com/CVE-2026-53182/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53182
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53182
- OSV: https://osv.dev/vulnerability/CVE-2026-53182

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53182/
Summaries are generated and may contain mistakes; the official description above is the record.
