Linux Kernel: security vulnerability (CVE-2026-72339)
Published Last modified Sources: SUSE, Ubuntu, CVE.org, BSI
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: qede: fix off-by-one in BD ring consumption on build_skb failure qede_rx_build_skb() and qede_tpa_rx_build_skb() do not check for a NULL return from qede_build_skb(). When it returns NULL under memory pressure, the functions still consume a BD from the ring before returning NULL.
Update Linux Kernel to version 5.10.261, Linux Kernel to version 5.15.212, Linux Kernel to version 6.1.178.
- Affected
- Linux Kernel
lt 4.18..5.10.261 - Linux Kernel
lt 5.11..5.15.212 - Linux Kernel
lt 5.16..6.1.178 - Linux Kernel
lt 6.2..6.6.145 - Linux Kernel
lt 6.7..6.12.97 - Linux Kernel
lt 6.13..6.18.40 - Linux Kernel
lt 6.19..7.1.5
- Linux Kernel
- Fixed in
- Linux Kernel
5.10.261 - Linux Kernel
5.15.212 - Linux Kernel
6.1.178 - Linux Kernel
6.6.145 - Linux Kernel
6.12.97 - Linux Kernel
6.18.40 - Linux Kernel
7.1.5 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: SUSE, Ubuntu, CVE.org, BSI
0.8 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 54.9
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 95.71 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.8 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 54.9
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 16 October 2026
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: qede: fix off-by-one in BD ring consumption on build_skb failure qede_rx_build_skb() and qede_tpa_rx_build_skb() do not check for a NULL return from qede_build_skb(). When it returns NULL under memory pressure, the functions still consume a BD from the ring before returning NULL. The callers then recycle additional BDs, resulting in one extra BD being consumed (off-by-one). This desynchronizes the BD ring, which can corrupt DMA page reference counts and lead to SLUB freelist corruption. Commit 4e910dbe3650 ("qede: confirm skb is allocated before using") added a NULL check inside qede_build_skb() to prevent a NULL pointer dereference, but did not address the missing NULL checks in the callers, making this off-by-one reachable. Fix this by adding NULL checks for the return value of qede_build_skb() in both qede_rx_build_skb() and qede_tpa_rx_build_skb(), returning NULL immediately before any BD ring manipulation.
Source: suse_csaf, Ubuntu Security Notices, cvelistv5, NVD (NIST), BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | linux | noble |
| Linux | ubuntu | linux | resolute |
| Linux | ubuntu | linux-aws | noble |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-aws-7.0 | noble |
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-azure | noble |
| Linux | ubuntu | linux-azure | resolute |
| Linux | ubuntu | linux-azure-7.0 | noble |
| Linux | ubuntu | linux-azure-fde | noble |
| Linux | ubuntu | linux-azure-fde | resolute |
| Linux | ubuntu | linux-azure-fde-7.0 | noble |
| Linux | ubuntu | linux-azure-fips | noble |
| Linux | ubuntu | linux-fips | noble |
| Linux | ubuntu | linux-gcp | noble |
| Linux | ubuntu | linux-gcp-fips | noble |
| Linux | ubuntu | linux-gke | noble |
| Linux | ubuntu | linux-gkeop | noble |
| Linux | ubuntu | linux-hwe-7.0 | noble |
| Linux | ubuntu | linux-ibm | noble |
| Linux | ubuntu | linux-ibm | resolute |
| Linux | ubuntu | linux-lowlatency | noble |
| Linux | ubuntu | linux-nvidia | jammy |
| Linux | ubuntu | linux-nvidia-7.0 | noble |
References & sources
- git.kernel.orgstable/c/ecc05d4b20220a09c9c69584fc46ca55248a374a
- git.kernel.orgstable/c/07be8b8adf91b7ada4c3dacce064d572a6066421
- git.kernel.orgstable/c/1624aa100c0b218181aa74e3696a389b509298cb
- git.kernel.orgstable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153
- git.kernel.orgstable/c/814a5edac8c9fc04051808d5faaa93768e989281
- git.kernel.orgstable/c/b066420e57f3402a52c998678b4678252ac9bb63
- git.kernel.orgstable/c/982d6d6bc059c5dff37a2201c2f08c14bcfcbd20
- git.kernel.orgstable/c/a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
New references:- https://git.kernel.org/stable/c/07be8b8adf91b7ada4c3dacce064d572a6066421
- https://git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153
- https://git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cb
- https://git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281
and 4 more references
Show 16 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/07be8b8adf91b7ada4c3dacce064d572a6066421Reference added —https://git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153Reference added —https://git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cbReference added —https://git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281Reference added —https://git.kernel.org/stable/c/982d6d6bc059c5dff37a2201c2f08c14bcfcbd20Reference added —https://git.kernel.org/stable/c/a0a558ca7e75b49e71f8c545c30e8c005e6e4e2fReference added —https://git.kernel.org/stable/c/b066420e57f3402a52c998678b4678252ac9bb63Reference added —https://git.kernel.org/stable/c/ecc05d4b20220a09c9c69584fc46ca55248a374aReference removed https://git.kernel.org/stable/c/07be8b8adf91b7ada4c3dacce064d572a6066421—Reference removed https://git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153—Reference removed https://git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cb—Reference removed https://git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281—Reference removed https://git.kernel.org/stable/c/982d6d6bc059c5dff37a2201c2f08c14bcfcbd20—Reference removed https://git.kernel.org/stable/c/a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f—Reference removed https://git.kernel.org/stable/c/b066420e57f3402a52c998678b4678252ac9bb63—Reference removed https://git.kernel.org/stable/c/ecc05d4b20220a09c9c69584fc46ca55248a374a—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-72339","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-16T18:47:21.272710Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedLinux
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/07be8b8adf91b7ada4c3dacce064d572a6066421
- https://git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153
- https://git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cb
- https://git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281
and 4 more references
Show 10 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Linux, LinuxDescription added —In the Linux kernel, the following vulnerability has been resolved: qede: fix off-by-one in BD ring consumption on build_skb failure qede_rx_build_skb() and qede_tpa_rx_build_skb() do not check for a NULL return from qede_build_skb(). When it returns NULL under memory pressure, the functions still consume a BD from the ring before returning NULL. The callers then recycle additional BDs, resulting in one extra BD being consumed (off-by-one). This desynchronizes the BD ring, which can corrupt DMA page reference counts and lead to SLUB freelist corruption. Commit 4e910dbe3650 ("qede: confirm skb is allocated before using") added a NULL check inside qede_build_skb() to prevent a NULL pointer dereference, but did not address the missing NULL checks in the callers, making this off-by-one reachable. Fix this by adding NULL checks for the return value of qede_build_skb() in both qede_rx_build_skb() and qede_tpa_rx_build_skb(), returning NULL immediately before any BD ring manipulation.Reference added —https://git.kernel.org/stable/c/07be8b8adf91b7ada4c3dacce064d572a6066421Reference added —https://git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153Reference added —https://git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cbReference added —https://git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281Reference added —https://git.kernel.org/stable/c/982d6d6bc059c5dff37a2201c2f08c14bcfcbd20Reference added —https://git.kernel.org/stable/c/a0a558ca7e75b49e71f8c545c30e8c005e6e4e2fReference added —https://git.kernel.org/stable/c/b066420e57f3402a52c998678b4678252ac9bb63Reference added —https://git.kernel.org/stable/c/ecc05d4b20220a09c9c69584fc46ca55248a374aSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-72339"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-72339.svg?lang=en" alt="CVE-2026-72339 – NEOSEC Intel" height="20"></a>