← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72339

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72339

Key Details

CVECVE-2026-72339
CVSS Score / Version
9.8 (Critical) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72339
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72339
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.