Answer in brief
CVE-2026-64093 records a Unknown severity vulnerability in batman-adv: tp_meter: directly shut down timer on 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-64093 records a Unknown severity vulnerability in batman-adv: tp_meter: directly shut down timer on 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 | >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <74a76634055462833446684fd526d73c290ea43a || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <5bc2d50fb66b46f86543d5153a188eb1486d0b6e || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <f86b20ec8d17d77bddc02c5c86cfa2389d84ecff || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <770bf0a35f0620b526fd4193889d1e77084e4c43 || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <933880a8bc9b4042223a79255c0b1021cdc36991 || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <d5487249a81ea658717614009c8f46acc5b7101a | 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 74a76634055462833446684fd526d73c290ea43a, 5bc2d50fb66b46f86543d5153a188eb1486d0b6e, f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, 770bf0a35f0620b526fd4193889d1e77084e4c43, 933880a8bc9b4042223a79255c0b1021cdc36991, d5487249a81ea658717614009c8f46acc5b7101a |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup batadv_tp_sender_cleanup() was calling timer_delete_sync() followed by timer_delete() to guard against the timer handler re-arming itself between the two calls. This double-deletion hack relied on the sending status being set to 0 to suppress re-arming. Replace both calls with a single timer_shutdown_sync(). This function both waits for any running timer callback to complete (like timer_delete_sync()) and permanently disarms the timer so it cannot be re-armed afterwards, making re-arming prevention unconditional and self-documenting. The re-arming property is also required because otherwise: 1. context 0 (batadv_tp_recv_ack()) checks in batadv_tp_reset_sender_timer() if sending is still 1 -> it is 2. context 1 changes in batadv_tp_sender_shutdown() sending to 0 and in this process forces the kthread to stop timer in batadv_tp_sender_cleanup() 3. context 0 continues in batadv_tp_reset_sender_timer() and rearms the timer -> but the reference for it is already gone
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 | >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <74a76634055462833446684fd526d73c290ea43a || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <5bc2d50fb66b46f86543d5153a188eb1486d0b6e || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <f86b20ec8d17d77bddc02c5c86cfa2389d84ecff || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <770bf0a35f0620b526fd4193889d1e77084e4c43 || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <933880a8bc9b4042223a79255c0b1021cdc36991 || >=33a3bb4a3345bb511f9c69c913da95d4693e2a4e <d5487249a81ea658717614009c8f46acc5b7101a | 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 74a76634055462833446684fd526d73c290ea43a, 5bc2d50fb66b46f86543d5153a188eb1486d0b6e, f86b20ec8d17d77bddc02c5c86cfa2389d84ecff, 770bf0a35f0620b526fd4193889d1e77084e4c43, 933880a8bc9b4042223a79255c0b1021cdc36991, d5487249a81ea658717614009c8f46acc5b7101a |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup batadv_tp_sender_cleanup() was calling timer_delete_sync() followed by timer_delete() to guard against the timer handler re-arming itself between the two calls. This double-deletion hack relied on the sending status being set to 0 to suppress re-arming. Replace both calls with a single timer_shutdown_sync(). This function both waits for any running timer callback to complete (like timer_delete_sync()) and permanently disarms the timer so it cannot be re-armed afterwards, making re-arming prevention unconditional and self-documenting. The re-arming property is also required because otherwise: 1. context 0 (batadv_tp_recv_ack()) checks in batadv_tp_reset_sender_timer() if sending is still 1 -> it is 2. context 1 changes in batadv_tp_sender_shutdown() sending to 0 and in this process forces the kthread to stop timer in batadv_tp_sender_cleanup() 3. context 0 continues in batadv_tp_reset_sender_timer() and rearms the timer -> but the reference for it is already gone
Quoted source text, attributed separately from HOL analysis.