Skip to main content
VulnerabilityPublished Updated

CVE-2026-68354: Linux kernel · firewire: net: Fix fragmented datagram reassembly

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in d52a13adbb8ccbab99cd3bad36804e87d8b5c052 : patch Linux kernel soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in d52a13adbb8ccbab99cd3bad36804e87d8b5c052, b7d633c7c92321be98724b1d365e8ce507f2f349, 268cea3800eda5fa3ee04a49ee2973b8766a8df3 +5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < d52a13adbb8ccbab99cd3bad36804e87d8b5c052
Fixed in
  • d52a13adbb8ccbab99cd3bad36804e87d8b5c052
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < b7d633c7c92321be98724b1d365e8ce507f2f349
Fixed in
  • b7d633c7c92321be98724b1d365e8ce507f2f349
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < 268cea3800eda5fa3ee04a49ee2973b8766a8df3
Fixed in
  • 268cea3800eda5fa3ee04a49ee2973b8766a8df3
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < 0177e578d7a885037b0fb82286c12e9d0360cc10
Fixed in
  • 0177e578d7a885037b0fb82286c12e9d0360cc10
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < 22e05b8ddbcf7d22c7f1598786e86635547e554d
Fixed in
  • 22e05b8ddbcf7d22c7f1598786e86635547e554d
LinuxLinuxAffected
  • ≥ c76acec6d55107b652a37c90b36c00bc8b04dabb, < 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999
Fixed in
  • 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999

Description

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.

References

Community reviews

Loading reviews…