Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 5bc2d50fb66b46f86543d5153a188eb1486d0b6e, 74a76634055462833446684fd526d73c290ea43a.

Low priority for now. Upgrade to Linux Linux 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785c, 5bc2d50fb66b46f86543d5153a188eb1486d0b6e, 74a76634055462833446684fd526d73c290ea43a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jul 19, 2026
Updated
Aug 11, 2026
EPSS
0.3% · 28th percentile
CWE
—

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
—
CNA · Linux
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64093

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.8 and later · before 5.15.210
  • linux linux kernel5.16 and later · before 6.1.176
  • linux linux kernel6.2 and later · before 6.6.143
  • linux linux kernel6.7 and later · before 6.12.93
  • linux linux kernel6.13 and later · before 6.18.34
  • linux linux kernel6.19 and later · before 7.0.11
  • linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.8affected
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 00bf4bb9947b1190a8be8d9b6a1bcbfa3707785caffected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 74a76634055462833446684fd526d73c290ea43aaffected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 5bc2d50fb66b46f86543d5153a188eb1486d0b6eaffected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before f86b20ec8d17d77bddc02c5c86cfa2389d84ecffaffected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 770bf0a35f0620b526fd4193889d1e77084e4c43affected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before 933880a8bc9b4042223a79255c0b1021cdc36991affected · git
    • 33a3bb4a3345bb511f9c69c913da95d4693e2a4e and later · before d5487249a81ea658717614009c8f46acc5b7101aaffected · git
    • before 4.8not affected · semver
    • 5.15.210 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 7.0.12-17.0.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64091Jul 19, 2026 · batman-adv: tt: fix TOCTOU race for reported vlans
    39Monitor
  • ← EarlierCVE-2026-64092Jul 19, 2026 · batman-adv: tp_meter: fix tp_vars reference leak in receiver shutdown
    22Monitor
  • Later →CVE-2026-64094Jul 19, 2026 · batman-adv: bla: avoid NULL-ptr deref for claim via dropped interface
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux00bf4bb9947b1190a8be8d9b6a1bcbfa3707785cVendor (CNA)
Linux Linux5bc2d50fb66b46f86543d5153a188eb1486d0b6eVendor (CNA)
Linux Linux74a76634055462833446684fd526d73c290ea43aVendor (CNA)
Linux Linux770bf0a35f0620b526fd4193889d1e77084e4c43Vendor (CNA)
Linux Linux933880a8bc9b4042223a79255c0b1021cdc36991Vendor (CNA)
Linux Linuxd5487249a81ea658717614009c8f46acc5b7101aVendor (CNA)
Linux Linuxf86b20ec8d17d77bddc02c5c86cfa2389d84ecffVendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records