CVE-2026-72056
net: ena: clean up XDP TX queues when regular TX setup fails
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 548c4940b9f1f527f81509468dd60b61418880b6; < df65d9fea8437235e740552e542fb309765507db (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 5daa63404b708fc74e94da8398affbb148d09044 (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 523caef03124ecc08ce62a78c617759c2d28cf1c (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < f2ff634d95f8a6c885b9ce71a64067e255bcc34a (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 6773d6d82bdabddab2b31605d6d7029c91dbd217 (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 6596baf8041100a9d1647beb5ea8ea4496ce058f (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 11f68ebc6891d11de5f32b7dee918c5dc18b8de1 (affected, git) ≥ 548c4940b9f1f527f81509468dd60b61418880b6; < 1bd6676254b4ab6acd44b662b5e92822c036463a (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.6 (affected) ≥ 0; < 5.6 (unaffected, semver) ≥ 5.10.261; ≤ 5.10.* (unaffected, semver) ≥ 5.15.212; ≤ 5.15.* (unaffected, semver) ≥ 6.1.178; ≤ 6.1.* (unaffected, semver) ≥ 6.6.145; ≤ 6.6.* (unaffected, semver) ≥ 6.12.97; ≤ 6.12.* (unaffected, semver) ≥ 6.18.40; ≤ 6.18.* (unaffected, semver) ≥ 7.1.5; ≤ 7.1.* (unaffected, semver) ≥ 7.2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/df65d9fea8437235e740552e542fb309765507dbCNA: Linux
- https://git.kernel.org/stable/c/5daa63404b708fc74e94da8398affbb148d09044CNA: Linux
- https://git.kernel.org/stable/c/523caef03124ecc08ce62a78c617759c2d28cf1cCNA: Linux
- https://git.kernel.org/stable/c/f2ff634d95f8a6c885b9ce71a64067e255bcc34aCNA: Linux
- https://git.kernel.org/stable/c/6773d6d82bdabddab2b31605d6d7029c91dbd217CNA: Linux
- https://git.kernel.org/stable/c/6596baf8041100a9d1647beb5ea8ea4496ce058fCNA: Linux
- https://git.kernel.org/stable/c/11f68ebc6891d11de5f32b7dee918c5dc18b8de1CNA: Linux
- https://git.kernel.org/stable/c/1bd6676254b4ab6acd44b662b5e92822c036463aCNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.