Answer in brief
CVE-2026-72339 records a Unknown severity vulnerability in qede: fix off-by-one in BD ring consumption on build_skb failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72339 records a Unknown severity vulnerability in qede: fix off-by-one in BD ring consumption on build_skb failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a8633978b842c88fbcfe00d4e5dde96048f630e <ecc05d4b20220a09c9c69584fc46ca55248a374a || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <07be8b8adf91b7ada4c3dacce064d572a6066421 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <1624aa100c0b218181aa74e3696a389b509298cb || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <0bf78df2d3ecb1f4964ff42a7327d25845955153 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <814a5edac8c9fc04051808d5faaa93768e989281 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <b066420e57f3402a52c998678b4678252ac9bb63 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <982d6d6bc059c5dff37a2201c2f08c14bcfcbd20 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f | ecc05d4b20220a09c9c69584fc46ca55248a374a, 07be8b8adf91b7ada4c3dacce064d572a6066421, 1624aa100c0b218181aa74e3696a389b509298cb, 0bf78df2d3ecb1f4964ff42a7327d25845955153, 814a5edac8c9fc04051808d5faaa93768e989281, b066420e57f3402a52c998678b4678252ac9bb63, 982d6d6bc059c5dff37a2201c2f08c14bcfcbd20, a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a8633978b842c88fbcfe00d4e5dde96048f630e <ecc05d4b20220a09c9c69584fc46ca55248a374a || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <07be8b8adf91b7ada4c3dacce064d572a6066421 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <1624aa100c0b218181aa74e3696a389b509298cb || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <0bf78df2d3ecb1f4964ff42a7327d25845955153 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <814a5edac8c9fc04051808d5faaa93768e989281 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <b066420e57f3402a52c998678b4678252ac9bb63 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <982d6d6bc059c5dff37a2201c2f08c14bcfcbd20 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f | ecc05d4b20220a09c9c69584fc46ca55248a374a, 07be8b8adf91b7ada4c3dacce064d572a6066421, 1624aa100c0b218181aa74e3696a389b509298cb, 0bf78df2d3ecb1f4964ff42a7327d25845955153, 814a5edac8c9fc04051808d5faaa93768e989281, b066420e57f3402a52c998678b4678252ac9bb63, 982d6d6bc059c5dff37a2201c2f08c14bcfcbd20, a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.