In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup… (CVE-2026-64093)
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
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's batman-adv tp_meter component stemmed from the batadv_tp_sender_cleanup() function calling timer_delete_sync() followed by timer_delete() to prevent the timer handler from re-arming itself between calls. This approach relied on a sending status flag to suppress re-arming, which was insufficient. The fix replaces these calls with timer_shutdown_sync(), which waits for any running timer callback to complete and permanently disarms the timer, preventing any re-arming. This addresses a race condition where one context could re-arm the timer after its reference was removed by another context, potentially leading to undefined behavior.
Potential Impact
The vulnerability could lead to a race condition or use-after-free scenario in the timer handling of the batman-adv module, potentially causing kernel instability or crashes. No known exploits in the wild have been reported. The impact is limited to the affected kernel module and involves kernel timer management.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing the double timer deletion calls with a single call to timer_shutdown_sync(). Users should update to the Linux kernel version that includes this fix once available. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories or vendor sources for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: directly shut down timer on cleanup… (CVE-2026-64093)
Description
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
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's batman-adv tp_meter component stemmed from the batadv_tp_sender_cleanup() function calling timer_delete_sync() followed by timer_delete() to prevent the timer handler from re-arming itself between calls. This approach relied on a sending status flag to suppress re-arming, which was insufficient. The fix replaces these calls with timer_shutdown_sync(), which waits for any running timer callback to complete and permanently disarms the timer, preventing any re-arming. This addresses a race condition where one context could re-arm the timer after its reference was removed by another context, potentially leading to undefined behavior.
Potential Impact
The vulnerability could lead to a race condition or use-after-free scenario in the timer handling of the batman-adv module, potentially causing kernel instability or crashes. No known exploits in the wild have been reported. The impact is limited to the affected kernel module and involves kernel timer management.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing the double timer deletion calls with a single call to timer_shutdown_sync(). Users should update to the Linux kernel version that includes this fix once available. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories or vendor sources for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-qf88-xw8w-824g
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64093"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912bf06
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:51:14 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.