Answer in brief
CVE-2026-72056 records a Unknown severity vulnerability in net: ena: clean up XDP TX queues when regular TX setup fails. 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-72056 records a Unknown severity vulnerability in net: ena: clean up XDP TX queues when regular TX setup fails. 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 | >=548c4940b9f1f527f81509468dd60b61418880b6 <df65d9fea8437235e740552e542fb309765507db || >=548c4940b9f1f527f81509468dd60b61418880b6 <5daa63404b708fc74e94da8398affbb148d09044 || >=548c4940b9f1f527f81509468dd60b61418880b6 <523caef03124ecc08ce62a78c617759c2d28cf1c || >=548c4940b9f1f527f81509468dd60b61418880b6 <f2ff634d95f8a6c885b9ce71a64067e255bcc34a || >=548c4940b9f1f527f81509468dd60b61418880b6 <6773d6d82bdabddab2b31605d6d7029c91dbd217 || >=548c4940b9f1f527f81509468dd60b61418880b6 <6596baf8041100a9d1647beb5ea8ea4496ce058f || >=548c4940b9f1f527f81509468dd60b61418880b6 <11f68ebc6891d11de5f32b7dee918c5dc18b8de1 || >=548c4940b9f1f527f81509468dd60b61418880b6 <1bd6676254b4ab6acd44b662b5e92822c036463a | df65d9fea8437235e740552e542fb309765507db, 5daa63404b708fc74e94da8398affbb148d09044, 523caef03124ecc08ce62a78c617759c2d28cf1c, f2ff634d95f8a6c885b9ce71a64067e255bcc34a, 6773d6d82bdabddab2b31605d6d7029c91dbd217, 6596baf8041100a9d1647beb5ea8ea4496ce058f, 11f68ebc6891d11de5f32b7dee918c5dc18b8de1, 1bd6676254b4ab6acd44b662b5e92822c036463a |
| Linux/Linuxgeneric | 5.6 | 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: 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.
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 | >=548c4940b9f1f527f81509468dd60b61418880b6 <df65d9fea8437235e740552e542fb309765507db || >=548c4940b9f1f527f81509468dd60b61418880b6 <5daa63404b708fc74e94da8398affbb148d09044 || >=548c4940b9f1f527f81509468dd60b61418880b6 <523caef03124ecc08ce62a78c617759c2d28cf1c || >=548c4940b9f1f527f81509468dd60b61418880b6 <f2ff634d95f8a6c885b9ce71a64067e255bcc34a || >=548c4940b9f1f527f81509468dd60b61418880b6 <6773d6d82bdabddab2b31605d6d7029c91dbd217 || >=548c4940b9f1f527f81509468dd60b61418880b6 <6596baf8041100a9d1647beb5ea8ea4496ce058f || >=548c4940b9f1f527f81509468dd60b61418880b6 <11f68ebc6891d11de5f32b7dee918c5dc18b8de1 || >=548c4940b9f1f527f81509468dd60b61418880b6 <1bd6676254b4ab6acd44b662b5e92822c036463a | df65d9fea8437235e740552e542fb309765507db, 5daa63404b708fc74e94da8398affbb148d09044, 523caef03124ecc08ce62a78c617759c2d28cf1c, f2ff634d95f8a6c885b9ce71a64067e255bcc34a, 6773d6d82bdabddab2b31605d6d7029c91dbd217, 6596baf8041100a9d1647beb5ea8ea4496ce058f, 11f68ebc6891d11de5f32b7dee918c5dc18b8de1, 1bd6676254b4ab6acd44b662b5e92822c036463a |
| Linux/Linuxgeneric | 5.6 | 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: 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.
Quoted source text, attributed separately from HOL analysis.