BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-64089High confidence

batman-adv: tt: fix negative last_changeset_len

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.55% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-64089 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-64089
323 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix negative last_changeset_len batadv_piv_tt::last_changeset_len len was declared as s16, but the field is never intended to hold a negative value. When a value greater than 32767 is assigned, it wraps to a negative signed integer. In batadv_send_my_tt_response(), last_changeset_len is temporarily widened to s32. The incorrectly negative s16 value propagates into the s32, causing batadv_tt_prepare_tvlv_local_data() to allocate a full sized buffer but populates only a small portion of it with the collected changeset. All remaining bits are kept uninitialized. Using an u16 avoids this type confusion and ensures that no (negative) sign extension is performed in batadv_send_my_tt_response().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45774

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix negative last_changeset_len batadv_piv_tt::last_changeset_len len was declared as s16, but the field is never intended to hold a negative value. When a value greater than 32767 is assigned, it wraps to a negative signed integer. In batadv_send_my_tt_response(), last_changeset_len is temporarily widened to s32. The incorrectly negative s16 value propagates into the s32, causing batadv_tt_prepare_tvlv_local_data() to allocate a full sized buffer but populates only a small portion of it with the collected changeset. All remaining bits are kept uninitialized. Using an u16 avoids this type confusion and ensures that no (negative) sign extension is performed in batadv_send_my_tt_response().

What

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix negative last_changeset_len batadv_piv_tt::last_changeset_len len was declared as s16, but the field is never intended to hold a negative value. When a value greater than 32767 is assigned, it wraps to a negative signed integer. In batadv_send_my_tt_response(), last_changeset_len is temporarily widened to s32. The incorrectly negative s16 value propagates into the s32, causing batadv_tt_prepare_tvlv_local_data() to allocate a full sized buffer but populates only a small portion of it with the collected changeset. All remaining bits are kept uninitialized. Using an u16 avoids this type confusion and ensures that no (negative) sign extension is performed in batadv_send_my_tt_response().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix negative last_changeset_len batadv_piv_tt::last_changeset_len len was declared as s16, but the field is never intended to hold a negative value. When a value greater than 32767 is assigned, it wraps to a negative signed integer. In batadv_send_my_tt_response(), last_changeset_len is temporarily widened to s32. The incorrectly negative s16 value propagates into the s32, causing batadv_tt_prepare_tvlv_local_data() to allocate a full sized buffer but populates only a small portion of it with the collected changeset. All remaining bits are kept uninitialized. Using an u16 avoids this type confusion and ensures that no (negative) sign extension is performed in batadv_send_my_tt_response().

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64092 https://www.cve.org/CVERecord?id=CVE-2026-64092 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-64056 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64104 https://www.cve.org/CVERecord?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64092 https://www.cve.org/CVERecord?id=CVE-2026-64092 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64092 https://www.cve.org/CVERecord?id=CVE-2026-64092 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=CVE-2026-64098 Référence CVE CVE-2026-64099 https://www.cve.org/CVERecord?id=CVE-2026-64099 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64092 https://www.cve.org/CVERecord?id=CVE-2026-64092 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64047 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-63968 Référence CVE CVE-2026-63971 https://www.cve.org/CVERecord?id=CVE-2026-63971 Référence CVE CVE-2026-63974 https://www.cve.org/CVERecord?id=CVE-2026-63974 Référence CVE CVE-2026-63975 https://www.cve.org/CVERecord?id=CVE-2026-63975 Référence CVE CVE-2026-63976 https://www.cve.org/CVERecord?id=CVE-2026-63976 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63991 https://www.cve.org/CVERecord?id=CVE-2026-63991 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64025 https://www.cve.org/CVERecord?id=CVE-2026-64025 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64174 https://www.cve.org/CVERecord?id=CVE-2026-64174 Référence CVE CVE-2026-64179 https://www.cve.org/CVERecord?id=CVE-2026-64179 Référence CVE CVE-2026-64182 https://www.cve.org/CVERecord?id=CVE-2026-64182 Référence CVE CVE-2026-64183 https://www.cve.org/CVERecord?id=CVE-2026-64183 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64047 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64102 https://www.cve.org/CVERecord?id=CVE-2026-64102 Référence CVE CVE-2026-64103 https://www.cve.org/CVERecord?id=CVE-2026-64103 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=CVE-2026-64081 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64090 https://www.cve.org/CVERecord?id=CVE-2026-64090 Référence CVE CVE-2026-64091 https://www.cve.org/CVERecord?id=CVE-2026-64091 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=CVE-2026-64093 Référence CVE CVE-2026-64094 https://www.cve.org/CVERecord?id=CVE-2026-64094 Référence CVE CVE-2026-64095 https://www.cve.org/CVERecord?id=CVE-2026-64095 Référence CVE CVE-2026-64096 https://www.cve.org/CVERecord?id=CVE-2026-64096 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-027893LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。batman-adv: ttにおけるlast_changeset_lenの負の値になる問題の修正です。batadv_piv_ttのlast_changeset_lenはs16として宣言されていましたが、このフィールドは負の値を保持することを意図していません。32767を超える値が割り当てられると、符号付き整数として負の値に巻き戻ってしまいます。batadv_send_my_tt_response()では、last_changeset_lenが一時的にs32に拡張されていますが、誤った負のs16値がs32に伝播します。その結果、batadv_tt_prepare_tvlv_local_data()は完全なサイズのバッファを割り当てるものの、収集したchangesetのごく一部のみを格納し、残りの部分は初期化されずに保持されてしまいます。u16を使用することで、この型の混乱を避け、batadv_send_my_tt_response()内で負の符号拡張が行われないことが保証されます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.1, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 5 Aug 2026, 12:39 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45774
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45774↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64089 · cve.blacktree.nl