Answer in brief
CVE-2026-72252 records a High severity (CVSS 7.8) vulnerability in netfilter: nft_set_pipapo: don't leak bad clone into future transaction. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), 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.
CVSS is 7.8. 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), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3c4287f62044a90e73a561aa05fc46e62da173da <047e813324eac2ac60cddfb58bcdbd0144eadb09 || >=3c4287f62044a90e73a561aa05fc46e62da173da <610e3b73efaec3dd81a95dcda2421ad7d9795bd0 || >=3c4287f62044a90e73a561aa05fc46e62da173da <02b6b0e892aea582590671796fd6eff5b93ea93f || >=3c4287f62044a90e73a561aa05fc46e62da173da <e74f9680e1b64872a51cc7b5bda1edaaa08aa51f || >=3c4287f62044a90e73a561aa05fc46e62da173da <47e65eff50691f0a5b79d325e28d83ec1da43bcf | 047e813324eac2ac60cddfb58bcdbd0144eadb09, 610e3b73efaec3dd81a95dcda2421ad7d9795bd0, 02b6b0e892aea582590671796fd6eff5b93ea93f, e74f9680e1b64872a51cc7b5bda1edaaa08aa51f, 47e65eff50691f0a5b79d325e28d83ec1da43bcf |
| Linux/Linuxgeneric | >=3c4287f62044a90e73a561aa05fc46e62da173da <0ab7b1802f63ca5b288ea59acb467830b83abd6b || >=3c4287f62044a90e73a561aa05fc46e62da173da <cc53703f48558896295f565cd4f5e956d21b7af4 || >=3c4287f62044a90e73a561aa05fc46e62da173da <047e813324eac2ac60cddfb58bcdbd0144eadb09 || >=3c4287f62044a90e73a561aa05fc46e62da173da <610e3b73efaec3dd81a95dcda2421ad7d9795bd0 || >=3c4287f62044a90e73a561aa05fc46e62da173da <02b6b0e892aea582590671796fd6eff5b93ea93f || >=3c4287f62044a90e73a561aa05fc46e62da173da <e74f9680e1b64872a51cc7b5bda1edaaa08aa51f || >=3c4287f62044a90e73a561aa05fc46e62da173da <47e65eff50691f0a5b79d325e28d83ec1da43bcf | 0ab7b1802f63ca5b288ea59acb467830b83abd6b, cc53703f48558896295f565cd4f5e956d21b7af4, 047e813324eac2ac60cddfb58bcdbd0144eadb09, 610e3b73efaec3dd81a95dcda2421ad7d9795bd0, 02b6b0e892aea582590671796fd6eff5b93ea93f, e74f9680e1b64872a51cc7b5bda1edaaa08aa51f, 47e65eff50691f0a5b79d325e28d83ec1da43bcf |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 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: netfilter: nft_set_pipapo: don't leak bad clone into future transaction On memory allocation failure the cloned nft_pipapo_match can enter a bad state: - some fields can have their lookup tables resized while others did not - bits might have been toggled - scratch map can be undersized which also means m->bsize_max can be lower than what is required This means that the next insertion in the same batch can trigger out-of-bounds writes. Furthermore, a failure in the first can result in the bad clone to leak into the next transaction because the abort callback is never executed in this case (the upper layer saw an error and no attempt to allocate a transactional request was made). Record a state for the nft_pipapo_match structure: - NEW (pristine clone) - MOD (modified clone with good state) - ERR (potentially bogus content) Then make it so that deletes and insertions fail when the clone entered ERR state. In case the very first insert attempt results in an error, free the clone right away.
Quoted source text, attributed separately from HOL analysis.