CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure
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.74% (FIRST EPSS); higher than 55.2% of all records.
- 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 07be8b8adf91b7ada4c3dacce064d572a6066421, 0bf78df2d3ecb1f4964ff42a7327d25845955153, 1624aa100c0b218181aa74e3696a389b509298cb.
Low priority for now. Upgrade to Linux Linux 07be8b8adf91b7ada4c3dacce064d572a6066421, 0bf78df2d3ecb1f4964ff42a7327d25845955153, 1624aa100c0b218181aa74e3696a389b509298cb 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: 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.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- —
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.18affected
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before ecc05d4b20220a09c9c69584fc46ca55248a374aaffected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before 07be8b8adf91b7ada4c3dacce064d572a6066421affected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before 1624aa100c0b218181aa74e3696a389b509298cbaffected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before 0bf78df2d3ecb1f4964ff42a7327d25845955153affected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before 814a5edac8c9fc04051808d5faaa93768e989281affected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before b066420e57f3402a52c998678b4678252ac9bb63affected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before 982d6d6bc059c5dff37a2201c2f08c14bcfcbd20affected · git
- 8a8633978b842c88fbcfe00d4e5dde96048f630e and later · before a0a558ca7e75b49e71f8c545c30e8c005e6e4e2faffected · git
- before 4.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72337Aug 15, 2026 · Bluetooth: 6lowpan: avoid untracked enable work0Monitor
- ← EarlierCVE-2026-72338Aug 15, 2026 · net/sched: act_pedit: fix TOCTOU heap OOB write in tc offload31Monitor
- Later →CVE-2026-72341Aug 15, 2026 · net/mlx5e: Fix publication race for priv->channel_stats[]0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07be8b8adf91b7ada4c3dacce064d572a6066421 | Vendor (CNA) |
| Linux Linux | 0bf78df2d3ecb1f4964ff42a7327d25845955153 | Vendor (CNA) |
| Linux Linux | 1624aa100c0b218181aa74e3696a389b509298cb | Vendor (CNA) |
| Linux Linux | 814a5edac8c9fc04051808d5faaa93768e989281 | Vendor (CNA) |
| Linux Linux | 982d6d6bc059c5dff37a2201c2f08c14bcfcbd20 | Vendor (CNA) |
| Linux Linux | a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f | Vendor (CNA) |
| Linux Linux | b066420e57f3402a52c998678b4678252ac9bb63 | Vendor (CNA) |
| Linux Linux | ecc05d4b20220a09c9c69584fc46ca55248a374a | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
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.
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 researchersFinders, 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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/0bf78df2d3ecb1f4964ff42a7327d25845955153
- git.kernel.org/stable/c/1624aa100c0b218181aa74e3696a389b509298cb
- git.kernel.org/stable/c/814a5edac8c9fc04051808d5faaa93768e989281
- git.kernel.org/stable/c/982d6d6bc059c5dff37a2201c2f08c14bcfcbd20
- git.kernel.org/stable/c/a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f
- git.kernel.org/stable/c/b066420e57f3402a52c998678b4678252ac9bb63
- git.kernel.org/stable/c/ecc05d4b20220a09c9c69584fc46ca55248a374a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.