LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

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.
Prepared
Confidence
medium
Sources
8

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-40252Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux55482edc25f0606851de42e73618f813f310d009, 55482edc25f0606851de42e73618f813f310d009, 55482edc25f0606851de42e73618f813f310d009, 55482edc25f0606851de42e73618f813f310d009, 55482edc25f0606851de42e73618f813f310d009, 55482edc25f0606851de42e73618f813f310d009unaffected
LinuxLinux4.6, 0, 5.15.197, 6.1.159, 6.6.118, 6.12.60, 6.17.10, 6.18affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.