Threats Tagged 'cve-2026-64092'
View all threats tagged with 'cve-2026-64092'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-64092'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel's batman-adv module related to the tp_meter component has been fixed. The issue involved a reference leak of tp_vars during the receiver shutdown process due to flawed coordination between the timer handler and the stop function. This could lead to improper release of resources. The fix introduces an atomic variable to ensure only one side releases the reference, preventing the leak. Join the discussion | GCVE Database | 07/19/2026, 18:31:51 UTC Added: 07/19/2026, 19:38:16 UTC |
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: fix tp_vars reference leak in receiver shutdown The receiver shutdown timer handler, batadv_tp_receiver_shutdown(), is responsible for releasing the tp_vars reference it holds. However, the existing logic for coordinating this release with batadv_tp_stop_all() was flawed. timer_shutdown_sync() guarantees the timer will not fire again after it returns, but it returns non-zero only when the timer was pending at the time of the call. If the timer had already expired (and batadv_tp_stop_all() would unsucessfully try to rearm itself), batadv_tp_stop_all() skips its batadv_tp_vars_put(), and batadv_tp_receiver_shutdown() fails to put its own reference as well. Fix this by introducing a new atomic variable receiving that is set to 1 when the receiver is initialized and cleared atomically with atomic_xchg() by whichever side claims it first. Only the side that observes the transition from 1 to 0 is responsible for releasing the tp_vars timer reference, eliminating the uncertainty. Join the discussion | GCVE Database | 07/19/2026, 16:17:00 UTC Added: 07/21/2026, 19:59:23 UTC |
Showing 1 to 2 of 2 results