CVE-2026-72056

net: ena: clean up XDP TX queues when regular TX setup fails

N/A
Published: August 15, 2026 at 05:52 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: ena: clean up XDP TX queues when regular TX setup fails create_queues_with_size_backoff() creates XDP TX queues before setting up the regular TX path. If the subsequent allocation or creation of regular TX queues fails, the error handling paths omit the teardown of the XDP TX queues, leading to a resource leak. Fix this by explicitly destroying the XDP TX queue subset at the two missing failure points. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc7. An x86_64 allyesconfig build showed no new warnings. As we do not have an ENA device to test with, no runtime testing was able to be performed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 5.10.2615.6 ≤ v < 5.15.2125.6 ≤ v < 6.1.1785.6 ≤ v < 6.12.975.6 ≤ v < 6.18.405.6 ≤ v < 6.6.1455.6 ≤ v < 7.1.55.6 ≤ v < 7.25.6548c4940b9f1f527f81509468dd60b61418880b6
Vendor states this is fixed in 11f68ebc6891d11de5f32b7dee918c5dc18b8de1 (fixed)
Vendor states this is fixed in 1bd6676254b4ab6acd44b662b5e92822c036463a (fixed)
Vendor states this is fixed in 523caef03124ecc08ce62a78c617759c2d28cf1c (fixed)
Vendor states this is fixed in 5daa63404b708fc74e94da8398affbb148d09044 (fixed)
Vendor states this is fixed in 6596baf8041100a9d1647beb5ea8ea4496ce058f (fixed)
Vendor states this is fixed in 6773d6d82bdabddab2b31605d6d7029c91dbd217 (fixed)
Vendor states this is fixed in df65d9fea8437235e740552e542fb309765507db (fixed)
Vendor states this is fixed in f2ff634d95f8a6c885b9ce71a64067e255bcc34a (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card