CVE-2026-64093
Last modified
CVE-2026-64093 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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(). EPSS estimates a 0.34% chance of exploitation in the next 30 days.
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
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.8, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64093?
How severe is CVE-2026-64093?
How do I fix CVE-2026-64093?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64088In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64089In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6409A Denial of Service (DoS) vulnerability exists in the Protob…7.1
- CVE-2026-64090In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64091In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64092In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64094In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64095In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64096In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64097In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64098In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64099In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64093?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
