Answer in brief
CVE-2026-72406 records a Unknown severity vulnerability in net: sungem: fix probe error cleanup. 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-72406 records a Unknown severity vulnerability in net: sungem: fix probe error cleanup. 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 | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f3bd60b26814b7c3c57c629abb0857dfc76d214a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1d04fefb0c2a2de32d9cee22cdc2088be3758d1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <331c99029a1cee1111f82f63d15b3cdebefbd341 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a63eaf7605d1579cf3f551792e478cfaf5ac37d1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb73cdc50b6755e5c3a80a195b2708a39ada0230 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b15a3cc68e2450aa0edd94a74a7bdd45fcc17dd9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bc49e8746584564dba47d963d1916cc876fc6f6b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <36dea2f639249460d13f6ca66b2a9064187cd34d | f3bd60b26814b7c3c57c629abb0857dfc76d214a, f1d04fefb0c2a2de32d9cee22cdc2088be3758d1, 331c99029a1cee1111f82f63d15b3cdebefbd341, a63eaf7605d1579cf3f551792e478cfaf5ac37d1, fb73cdc50b6755e5c3a80a195b2708a39ada0230, b15a3cc68e2450aa0edd94a74a7bdd45fcc17dd9, bc49e8746584564dba47d963d1916cc876fc6f6b, 36dea2f639249460d13f6ca66b2a9064187cd34d |
| Linux/Linuxgeneric | 2.6.12 | 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: sungem: fix probe error cleanup gem_init_one() calls gem_remove_one() when register_netdev() fails. gem_remove_one() unregisters and frees resources owned by the net_device, including the DMA block, MMIO mapping, PCI regions, and the net_device itself. gem_init_one() then falls through to its own cleanup labels and frees the same resources again. Keep the register_netdev() error path in gem_init_one(): clear drvdata so PM/remove paths do not see a half-registered device, remove the NAPI instance added during probe, and let the existing cleanup labels release the resources once. The issue was found by a local static-analysis checker for probe error paths. The reported path was manually inspected before sending this fix. Compile-tested with CONFIG_SUNGEM=y. Runtime testing was not performed because no sungem hardware is available.
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 | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f3bd60b26814b7c3c57c629abb0857dfc76d214a || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1d04fefb0c2a2de32d9cee22cdc2088be3758d1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <331c99029a1cee1111f82f63d15b3cdebefbd341 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a63eaf7605d1579cf3f551792e478cfaf5ac37d1 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb73cdc50b6755e5c3a80a195b2708a39ada0230 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b15a3cc68e2450aa0edd94a74a7bdd45fcc17dd9 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bc49e8746584564dba47d963d1916cc876fc6f6b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <36dea2f639249460d13f6ca66b2a9064187cd34d | f3bd60b26814b7c3c57c629abb0857dfc76d214a, f1d04fefb0c2a2de32d9cee22cdc2088be3758d1, 331c99029a1cee1111f82f63d15b3cdebefbd341, a63eaf7605d1579cf3f551792e478cfaf5ac37d1, fb73cdc50b6755e5c3a80a195b2708a39ada0230, b15a3cc68e2450aa0edd94a74a7bdd45fcc17dd9, bc49e8746584564dba47d963d1916cc876fc6f6b, 36dea2f639249460d13f6ca66b2a9064187cd34d |
| Linux/Linuxgeneric | 2.6.12 | 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: sungem: fix probe error cleanup gem_init_one() calls gem_remove_one() when register_netdev() fails. gem_remove_one() unregisters and frees resources owned by the net_device, including the DMA block, MMIO mapping, PCI regions, and the net_device itself. gem_init_one() then falls through to its own cleanup labels and frees the same resources again. Keep the register_netdev() error path in gem_init_one(): clear drvdata so PM/remove paths do not see a half-registered device, remove the NAPI instance added during probe, and let the existing cleanup labels release the resources once. The issue was found by a local static-analysis checker for probe error paths. The reported path was manually inspected before sending this fix. Compile-tested with CONFIG_SUNGEM=y. Runtime testing was not performed because no sungem hardware is available.
Quoted source text, attributed separately from HOL analysis.