Answer in brief
CVE-2026-72231 records a Unknown severity vulnerability in batman-adv: tt: avoid request storms during pending request. 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-72231 records a Unknown severity vulnerability in batman-adv: tt: avoid request storms during pending request. 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 | >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <6055695ea40c64a47e00742c12c99b1a33b4daed || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <21c44a6895f41df811d1c91d10eea194dda2b345 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <5e46c76d9a5062212c4c5f642a5549fd9c057f8a || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <067e413eec2e63c2996909ef55214b3a0eda0be7 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <716f434eb35869e130424331584a91fbb729b9bd || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <6a65ac8a81e903bb4b555c1d13532f5cb0167a4a || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <aba1cf21954e64c36afb966b754adad2b0b8aa48 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <27c7d40008231ae4140d35501b60087a9de2d2c3 | 6055695ea40c64a47e00742c12c99b1a33b4daed, 21c44a6895f41df811d1c91d10eea194dda2b345, 5e46c76d9a5062212c4c5f642a5549fd9c057f8a, 067e413eec2e63c2996909ef55214b3a0eda0be7, 716f434eb35869e130424331584a91fbb729b9bd, 6a65ac8a81e903bb4b555c1d13532f5cb0167a4a, aba1cf21954e64c36afb966b754adad2b0b8aa48, 27c7d40008231ae4140d35501b60087a9de2d2c3 |
| Linux/Linuxgeneric | 3.13 | 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: batman-adv: tt: avoid request storms during pending request batadv_send_tt_request() allocates a tt_req_node when none exists for the destination originator node. This should prevent that a multiple TT requests are send at the same time to an originator. But if allocation of the send buffer failed, this request must be cleaned up again. But indicator for such a failure is "ret == false". But the actual implementation is checking for "ret == true". The check must be inverted to not loose the information about the TT request directly after it was attempted to be sent out. This should avoid potential request storms.
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 | >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <6055695ea40c64a47e00742c12c99b1a33b4daed || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <21c44a6895f41df811d1c91d10eea194dda2b345 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <5e46c76d9a5062212c4c5f642a5549fd9c057f8a || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <067e413eec2e63c2996909ef55214b3a0eda0be7 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <716f434eb35869e130424331584a91fbb729b9bd || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <6a65ac8a81e903bb4b555c1d13532f5cb0167a4a || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <aba1cf21954e64c36afb966b754adad2b0b8aa48 || >=335fbe0f5d2501b7dd815806aef6fd9bad784eb1 <27c7d40008231ae4140d35501b60087a9de2d2c3 | 6055695ea40c64a47e00742c12c99b1a33b4daed, 21c44a6895f41df811d1c91d10eea194dda2b345, 5e46c76d9a5062212c4c5f642a5549fd9c057f8a, 067e413eec2e63c2996909ef55214b3a0eda0be7, 716f434eb35869e130424331584a91fbb729b9bd, 6a65ac8a81e903bb4b555c1d13532f5cb0167a4a, aba1cf21954e64c36afb966b754adad2b0b8aa48, 27c7d40008231ae4140d35501b60087a9de2d2c3 |
| Linux/Linuxgeneric | 3.13 | 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: batman-adv: tt: avoid request storms during pending request batadv_send_tt_request() allocates a tt_req_node when none exists for the destination originator node. This should prevent that a multiple TT requests are send at the same time to an originator. But if allocation of the send buffer failed, this request must be cleaned up again. But indicator for such a failure is "ret == false". But the actual implementation is checking for "ret == true". The check must be inverted to not loose the information about the TT request directly after it was attempted to be sent out. This should avoid potential request storms.
Quoted source text, attributed separately from HOL analysis.