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

firewire: net: Fix fragmented datagram reassembly

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 111 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 severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.41% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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 30 daysRemediation target: Within 180 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 111 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.

25 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.101-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-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.

2 current
CVE-2026-68354 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-68354
298 known affected

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

  • 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
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68354 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: firewire: net: Fix fragmented datagram reassembly
91 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the FireWire (IEEE 1394) networking driver in the Linux kernel. The fragmented datagram reassembly logic in `fwnet_frag_new()` incorrectly handles list edges and merging of adjacent fragments. This can prevent complete datagrams from being recognized, potentially leading to a Denial of Service (DoS) for FireWire network communication.
Remediation
To mitigate this issue, prevent the firewire_net module from loading. See https://access.redhat.com/solutions/41278 for instructions.
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-55455

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.

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
8.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 111 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: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.

What

In the Linux kernel, the following vulnerability has been resolved: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.

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 an adjacent network 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: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.

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 an adjacent network 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
an adjacent network → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
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:A/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.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close 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.
Unauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55455Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: firewire: net: Fix fragmented datagram reassembly fwnet_frag_new() keeps a sorted list of received fragments for a partial datagram. When a new fragment is adjacent to an existing fragment, the code checks whether the new fragment also closes the gap to the next or previous list entry. Those neighbor lookups currently assume that the current fragment always has a real next or previous fragment. At a list edge, the next or previous entry is the list head, not a struct fwnet_fragment_info. The gap checks also compare against the old edge of the current fragment instead of the edge after adding the new fragment. As a result, a fragment that bridges two existing ranges may leave two adjacent ranges unmerged, so fwnet_pd_is_complete() can miss a complete datagram. Check for the list head before looking up the neighboring fragment, and compare the neighbor against the new fragment's far edge when deciding whether to merge all three ranges. This issue was found by a static analysis checker and confirmed by manual source review.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2730Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-68340 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=CVE-2026-68357 Référence CVE CVE-2026-68358 https://www.cve.org/CVERecord?id=CVE-2026-68358 Référence CVE CVE-2026-68359 https://www.cve.org/CVERecord?id=CVE-2026-68359 Référence CVE CVE-2026-68360 https://www.cve.org/CVERecord?id=CVE-2026-68360 Référence CVE CVE-2026-68361 https://www.cve.org/CVERecord?id=CVE-2026-68361 Référence CVE CVE-2026-68362 https://www.cve.org/CVERecord?id=CVE-2026-68362 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68340 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=CVE-2026-68357 Référence CVE CVE-2026-68359 https://www.cve.org/CVERecord?id=CVE-2026-68359 Référence CVE CVE-2026-68360 https://www.cve.org/CVERecord?id=CVE-2026-68360 Référence CVE CVE-2026-68361 https://www.cve.org/CVERecord?id=CVE-2026-68361 Référence CVE CVE-2026-68362 https://www.cve.org/CVERecord?id=CVE-2026-68362 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=CVE-2026-68363 Référence CVE CVE-2026-68365 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68338 Référence CVE CVE-2026-68340 https://www.cve.org/CVERecord?id=CVE-2026-68340 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=CVE-2026-68357 Référence CVE CVE-2026-68359 https://www.cve.org/CVERecord?id=CVE-2026-68359 Référence CVE CVE-2026-68360 https://www.cve.org/CVERecord?id=CVE-2026-68360 Référence CVE CVE-2026-68361 https://www.cve.org/CVERecord?id=CVE-2026-68361 Référence CVE CVE-2026-68362 https://www.cve.org/CVERecord?id=CVE-2026-68362 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=CVE-2026-68363 Référence CVE CVE-2026-68365 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68340 Référence CVE CVE-2026-68343 https://www.cve.org/CVERecord?id=CVE-2026-68343 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=CVE-2026-68357 Référence CVE CVE-2026-68359 https://www.cve.org/CVERecord?id=CVE-2026-68359 Référence CVE CVE-2026-68360 https://www.cve.org/CVERecord?id=CVE-2026-68360 Référence CVE CVE-2026-68361 https://www.cve.org/CVERecord?id=CVE-2026-68361 Référence CVE CVE-2026-68362 https://www.cve.org/CVERecord?id=CVE-2026-68362 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=CVE-2026-68363 Référence CVE CVE-2026-68365 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68343 Référence CVE CVE-2026-68344 https://www.cve.org/CVERecord?id=CVE-2026-68344 Référence CVE CVE-2026-68346 https://www.cve.org/CVERecord?id=CVE-2026-68346 Référence CVE CVE-2026-68348 https://www.cve.org/CVERecord?id=CVE-2026-68348 Référence CVE CVE-2026-68349 https://www.cve.org/CVERecord?id=CVE-2026-68349 Référence CVE CVE-2026-68350 https://www.cve.org/CVERecord?id=CVE-2026-68350 Référence CVE CVE-2026-68351 https://www.cve.org/CVERecord?id=CVE-2026-68351 Référence CVE CVE-2026-68352 https://www.cve.org/CVERecord?id=CVE-2026-68352 Référence CVE CVE-2026-68353 https://www.cve.org/CVERecord?id=CVE-2026-68353 Référence CVE CVE-2026-68354 https://www.cve.org/CVERecord?id=CVE-2026-68354 Référence CVE CVE-2026-68355 https://www.cve.org/CVERecord?id=CVE-2026-68355 Référence CVE CVE-2026-68357 https://www.cve.org/CVERecord?id=CVE-2026-68357 Référence CVE CVE-2026-68358 https://www.cve.org/CVERecord?id=CVE-2026-68358 Référence CVE CVE-2026-68359 https://www.cve.org/CVERecord?id=CVE-2026-68359 Référence CVE CVE-2026-68360 https://www.cve.org/CVERecord?id=CVE-2026-68360 Référence CVE CVE-2026-68361 https://www.cve.org/CVERecord?id=CVE-2026-68361 Référence CVE CVE-2026-68362 https://www.cve.org/CVERecord?id=CVE-2026-68362 Référence CVE CVE-2026-68363 https://www.cve.org/CVERecord?id=

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: < 2.6.31, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 7.1.*, 7.2 ≤ *
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:34 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-55455
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

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 ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-68354 to remediation: access.redhat.com/CVE-2026-68354.
    Before
    remediation: access.redhat.com/CVE-2026-68354
    After
    remediation: access.redhat.com/CVE-2026-68354
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/1aaf16031d65ccd4576451a79f7dabbec994c111; removed remediation: git.kernel.org/b7d633c7c92321be98724b1d365e8ce507f2f349.
    Before
    remediation: git.kernel.org/b7d633c7c92321be98724b1d365e8ce507f2f349
    After
    remediation: git.kernel.org/1aaf16031d65ccd4576451a79f7dabbec994c111
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    c76acec6d55107b652a37c90b36c00bc8b04dabb < b7d633c7c92321be98724b1d365e8ce507f2f349; c76acec6d55107b652a37c90b36c00bc8b04dabb < 22e05b8ddbcf7d22c7f1598786e86635547e554d; c76acec6d55107b652a37c90b36c00bc8b04dabb < 0177e578d7a885037b0fb82286c12e9d0360cc10; c76acec6d55107b652a37c90b36c00bc8b04dabb < 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999; c76acec6d55107b652a37c90b36c00bc8b04dabb < d52a13adbb8ccbab99cd3bad36804e87d8b5c052; 2.6.31 · Fixed: < 2.6.31; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    c76acec6d55107b652a37c90b36c00bc8b04dabb < 1aaf16031d65ccd4576451a79f7dabbec994c111; c76acec6d55107b652a37c90b36c00bc8b04dabb < 0a219b2a01b4fe93706717e3bcacf7f62967b26f; c76acec6d55107b652a37c90b36c00bc8b04dabb < 268cea3800eda5fa3ee04a49ee2973b8766a8df3; c76acec6d55107b652a37c90b36c00bc8b04dabb < b7d633c7c92321be98724b1d365e8ce507f2f349; c76acec6d55107b652a37c90b36c00bc8b04dabb < 22e05b8ddbcf7d22c7f1598786e86635547e554d; c76acec6d55107b652a37c90b36c00bc8b04dabb < 0177e578d7a885037b0fb82286c12e9d0360cc10; c76acec6d55107b652a37c90b36c00bc8b04dabb < 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999; c76acec6d55107b652a37c90b36c00bc8b04dabb < d52a13adbb8ccbab99cd3bad36804e87d8b5c052 · Fixed: < 2.6.31; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    c76acec6d55107b652a37c90b36c00bc8b04dabb < b7d633c7c92321be98724b1d365e8ce507f2f349; c76acec6d55107b652a37c90b36c00bc8b04dabb < 22e05b8ddbcf7d22c7f1598786e86635547e554d; c76acec6d55107b652a37c90b36c00bc8b04dabb < 0177e578d7a885037b0fb82286c12e9d0360cc10; c76acec6d55107b652a37c90b36c00bc8b04dabb < 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999; c76acec6d55107b652a37c90b36c00bc8b04dabb < d52a13adbb8ccbab99cd3bad36804e87d8b5c052; 2.6.31 · Fixed: < 2.6.31; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    c76acec6d55107b652a37c90b36c00bc8b04dabb < b7d633c7c92321be98724b1d365e8ce507f2f349; c76acec6d55107b652a37c90b36c00bc8b04dabb < 22e05b8ddbcf7d22c7f1598786e86635547e554d; c76acec6d55107b652a37c90b36c00bc8b04dabb < 0177e578d7a885037b0fb82286c12e9d0360cc10; c76acec6d55107b652a37c90b36c00bc8b04dabb < 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999; c76acec6d55107b652a37c90b36c00bc8b04dabb < d52a13adbb8ccbab99cd3bad36804e87d8b5c052; 2.6.31 · Fixed: < 2.6.31; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
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-55455↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-68354 · cve.blacktree.nl