CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end()
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.
Security readout for executives and security teams
Plain-English summary
A Linux network-driver flaw can read beyond a fixed-size array when expected termination data is missing or malformed. Systems are potentially exposed only when the affected qede driver code is present and relevant. The supplied record rates it critical, but it does not document successful exploitation or confirmed real-world attacks.
Executive priority
Treat as an urgent patch-verification issue for systems actively using qede, especially critical network infrastructure. Do not classify the entire Linux estate as equally exposed. Establish driver usage first, then accelerate vendor-supported updates. Current evidence does not support declaring an active incident solely from this CVE.
Technical view
qede_tpa_cont() and qede_tpa_end() iterate over cqe->len_list[] until finding a zero-length entry. Without a valid terminator, iteration can exceed the array boundary. Linux stable fixes add ARRAY_SIZE() bounds to both loops. The supplied version data is ambiguous, so fixed status should be verified against kernel or distribution guidance.
Likely exposure
Prioritize Linux hosts using affected kernel branches with the qede network driver built, loaded, or actively serving traffic. Hosts without this driver code are less likely to be exposed. The bundled affected-version list contains unusual and duplicated entries, preventing reliable version-only conclusions without vendor confirmation.
Exploitation context
The supplied CVSS 3.1 score is 9.8 with network reachability, low complexity, no privileges, and no user interaction. However, the description establishes only a potential out-of-bounds read. The record is not in KEV, and the supplied sources provide no evidence of active exploitation, public weaponization, or demonstrated impact.
Researcher notes
No CWE is assigned in the supplied record. The stated critical CVSS impacts are broader than the description’s demonstrated potential out-of-bounds read. No crash, disclosure, corruption, or code-execution proof is supplied. Stable commits show the defensive bounds change, but branch-specific applicability must be mapped carefully.
Mitigation direction
Apply a vendor-supported kernel containing the applicable stable fix.
Check distribution and hardware-vendor advisories for precise fixed package versions.
Where patching is delayed, assess whether the qede driver can be safely disabled or avoided.
Prioritize exposed or operationally critical systems actively using the qede driver.
Validation and detection
Inventory kernel versions and determine whether the qede driver is built, loaded, or used.
Compare deployed kernel sources or packages with the applicable stable fix commit.
Confirm vendor package changelogs explicitly reference CVE-2025-40252 or the qede bounds fix.
After updating, verify the host runs the intended fixed kernel and retains expected networking.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-40252 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.