Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 896f1a2493b59beb2b5ccdf990503dbb16cb2256, 917a9d02182ac8b4f25eb47dc02f3ec679608c24, a778912b4a53587ea07d85526d152f85d109cbfe.

Low priority for now. Upgrade to Linux Linux 896f1a2493b59beb2b5ccdf990503dbb16cb2256, 917a9d02182ac8b4f25eb47dc02f3ec679608c24, a778912b4a53587ea07d85526d152f85d109cbfe or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.8 · v3.1—No exploit Fix available
Published
Dec 4, 2025
Updated
Oct 19, 2026
EPSS
0.6% · 48th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40252

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.6affected
    • 55482edc25f0606851de42e73618f813f310d009 and later · before ecbb12caf399d7cf364b7553ed5aebeaa2f255bcaffected · git
    • 55482edc25f0606851de42e73618f813f310d009 and later · before a778912b4a53587ea07d85526d152f85d109cbfeaffected · git
    • 55482edc25f0606851de42e73618f813f310d009 and later · before f0923011c1261b33a2ac1de349256d39cb750dd0affected · git
    • 55482edc25f0606851de42e73618f813f310d009 and later · before 917a9d02182ac8b4f25eb47dc02f3ec679608c24affected · git
    • 55482edc25f0606851de42e73618f813f310d009 and later · before e441db07f208184e0466abf44b389a81d70c340eaffected · git
    • 55482edc25f0606851de42e73618f813f310d009 and later · before 896f1a2493b59beb2b5ccdf990503dbb16cb2256affected · git
    • before 4.6not affected · semver
    • 5.15.197 and later · up to and including 5.15.*not affected · semver
    • 6.1.159 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.123.1.el8_104.18.0-553.123.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.123.1.rt7.464.el8_104.18.0-553.123.1.rt7.464.el8_10

+67

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40249Dec 4, 2025 · gpio: cdev: make sure the cdev fd is still active before emitting events
    31Monitor
  • ← EarlierCVE-2025-40250Dec 4, 2025 · net/mlx5: Clean up only new IRQ glue on request_irq() failure
    31Monitor
  • Later →CVE-2025-40253Dec 4, 2025 · s390/ctcm: Fix double-kfree
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux896f1a2493b59beb2b5ccdf990503dbb16cb2256Vendor (CNA)
Linux Linux917a9d02182ac8b4f25eb47dc02f3ec679608c24Vendor (CNA)
Linux Linuxa778912b4a53587ea07d85526d152f85d109cbfeVendor (CNA)
Linux Linuxe441db07f208184e0466abf44b389a81d70c340eVendor (CNA)
Linux Linuxecbb12caf399d7cf364b7553ed5aebeaa2f255bcVendor (CNA)
Linux Linuxf0923011c1261b33a2ac1de349256d39cb750dd0Vendor (CNA)
almalinux:bpftool4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.123.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.159-1~deb11u1 · Debian:11Package registry (OSV)
red hat:bpftool0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.123.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records