CVE-2026-64093
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
batman-adv: tp_meter: directly shut down timer on cleanup
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
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | 74a76634055462833446684fd526d73c290ea43a | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | 5bc2d50fb66b46f86543d5153a188eb1486d0b6e | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | f86b20ec8d17d77bddc02c5c86cfa2389d84ecff | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | 770bf0a35f0620b526fd4193889d1e77084e4c43 | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | 933880a8bc9b4042223a79255c0b1021cdc36991 | Unavailable | None listed |
| 33a3bb4a3345bb511f9c69c913da95d4693e2a4e | affected | git | d5487249a81ea658717614009c8f46acc5b7101a | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 4.8 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 4.8 | Unavailable | None listed |
| 5.15.210 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.1.176 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.143 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.93 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.34 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.0.11 | unaffected | semver | Unavailable | 7.0.* | None listed |
| 7.1 | unaffected | original_commit_for_fix | Unavailable | * | None listed |