CVE-2026-72339
CVE CVE-2026-72339EUVD EUVD-2026-59238Published 2026-08-15T05:55:46.000ZLast changed 2026-08-17T05:42:57.000ZCVSS 9.8
What the advisory describes
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: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 8a8633978b842c88fbcfe00d4e5dde96048f630e <814a5edac8c9fc04051808d5faaa93768e989281; patch: 6.1.178; 8a8633978b842c88fbcfe00d4e5dde96048f630e <0bf78df2d3ecb1f4964ff42a7327d25845955153; patch: 6.18.40; 8a8633978b842c88fbcfe00d4e5dde96048f630e <a0a558ca7e75b49e71f8c545c30e8c005e6e4e2f; 8a8633978b842c88fbcfe00d4e5dde96048f630e <07be8b8adf91b7ada4c3dacce064d572a6066421; patch: 5.10.261; 8a8633978b842c88fbcfe00d4e5dde96048f630e <ecc05d4b20220a09c9c69584fc46ca55248a374a; patch: 5.15.212; 8a8633978b842c88fbcfe00d4e5dde96048f630e <1624aa100c0b218181aa74e3696a389b509298cb; patch: 7.1.5; patch: 6.6.145; patch: 6.12.97; patch: 7.2; 4.18; 8a8633978b842c88fbcfe00d4e5dde96048f630e <982d6d6bc059c5dff37a2201c2f08c14bcfcbd20; 8a8633978b842c88fbcfe00d4e5dde96048f630e <b066420e57f3402a52c998678b4678252ac9bb63; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.