CVE-2026-64092 Vulnerability Analysis & Exploit Details

CVE-2026-64092
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2026-64092 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-64092 Details

Status: Analyzed

Last updated: 🕞 11 Aug 2026, 15:56 UTC
Originally published on: 🕓 19 Jul 2026, 16:17 UTC

Time between publication and last update: 22 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2026-64092 Vulnerability Summary

CVE-2026-64092: 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.

Assessing the Risk of CVE-2026-64092

Access Complexity Graph

The exploitability of CVE-2026-64092 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-64092

CVE-2026-64092 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-64092, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-64092, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-64092 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-64092 poses no threat to data integrity.
  • Availability: High
    CVE-2026-64092 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-64092 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.10.259:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.259:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.10.260:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.10.260:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.140:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.140:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.141:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.141:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.90:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.90:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.91:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.91:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.32:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.32:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.33:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.33:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-64092: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97876 – A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB mo...
  • CVE-2026-96990 – Allocation of Resources Without Limits or Throttling vulnerability in Apache Thrift Erlang bindings. This issue affects Apache Thrift: before 0....
  • CVE-2026-94651 – improper handling of exceptional conditions, Missing release of resource after effective lifetime vulnerability in Apache Thrift java bindings. ...
  • CVE-2026-94650 – Uncontrolled Recursion vulnerability in Apache Thrift c_glib bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended...
  • CVE-2026-94645 – Improper validation of specified quantity in input, Allocation of resources without limits or throttling vulnerability in Apache Thrift nodejs bind...