CVE-2026-68354

firewire: net: Fix fragmented datagram reassembly

HIGH
8.8
CVSS Score
Published: August 10, 2026 at 12:03 PM UTC
Updated: October 19, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.31c76acec6d55107b652a37c90b36c00bc8b04dabb
Vendor states this is fixed in 0177e578d7a885037b0fb82286c12e9d0360cc10 (fixed)
Vendor states this is fixed in 0a219b2a01b4fe93706717e3bcacf7f62967b26f (fixed)
Vendor states this is fixed in 1aaf16031d65ccd4576451a79f7dabbec994c111 (fixed)
Vendor states this is fixed in 22e05b8ddbcf7d22c7f1598786e86635547e554d (fixed)
Vendor states this is fixed in 268cea3800eda5fa3ee04a49ee2973b8766a8df3 (fixed)
Vendor states this is fixed in 2a5aa4e9b89227d1a1690fb8d5b81e5f3b261999 (fixed)
Vendor states this is fixed in b7d633c7c92321be98724b1d365e8ce507f2f349 (fixed)
Vendor states this is fixed in d52a13adbb8ccbab99cd3bad36804e87d8b5c052 (fixed)
Vendor states this is fixed in 2.6.31 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card