# CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()

> A missing bounds check in the QLogic qede network driver allows out-of-bounds reads, potentially causing crashes or leaking kernel memory.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-71393, BELL-CVE-2025-40252, DEBIAN-CVE-2025-40252, GHSA-j29x-hm96-8wj9, ROOT-OS-DEBIAN-11-CVE-2025-40252, ROOT-OS-DEBIAN-12-CVE-2025-40252, ROOT-OS-DEBIAN-13-CVE-2025-40252, ROOT-OS-UBUNTU-2204-CVE-2025-40252, ROOT-OS-UBUNTU-2404-CVE-2025-40252, UBUNTU-CVE-2025-40252

## What is CVE-2025-40252?

CVE-2025-40252 is a critical memory corruption vulnerability in Linux, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()

The loops in 'qede_tpa_cont()' and 'qede_tpa_end()', iterate
over 'cqe->len_list[]' using only a zero-length terminator as
the stopping condition. If the terminator was missing or
malformed, the loop could run past the end of the fixed-size array.

Add an explicit bound check using ARRAY_SIZE() in both loops to prevent
a potential out-of-bounds access.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

## Which versions are affected by CVE-2025-40252?


## How do I fix CVE-2025-40252?

Apply the vendor's patch.

## Is CVE-2025-40252 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40252 and fix it if it is affected.

What it is: CVE-2025-40252 is a critical memory corruption vulnerability in Linux, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40252 in the wild and no public exploit code.

Affected product: Linux. 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-2025-40252/ (Markdown: https://insights.sbomify.com/CVE-2025-40252/index.md)
```

## Sources

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

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