Skip to main content

Linux Kernel EUVDEUVD-2026-55455

| CVE-2026-68354 HIGH
2026-08-10 Linux GHSA-pcmh-x4q7-gxf9
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.8 HIGH

Physical IEEE 1394 bus adjacency required (AV:A); no OS privileges needed at driver level (PR:N); kernel type-confusion plausibly impacts all three dimensions if list-head dereference corrupts memory.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 03:01 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
8.8 (HIGH)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 12:03 cve.org
HIGH 8.8
CVE Published
Aug 10, 2026 - 12:03 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

FireWire network driver in the Linux kernel contains a linked-list boundary confusion flaw in fwnet_frag_new() that mishandles fragment reassembly at list edges, potentially enabling kernel memory corruption by adjacent-network attackers. Systems with the firewire-net module loaded are exposed to unauthenticated attackers sharing the same IEEE 1394 bus who can send crafted fragmented datagrams to trigger the defect. No public exploit exists and EPSS sits at 0.18% (7th percentile), but the CVSS 8.8 vector reflects high potential impact if type confusion against the list head leads to arbitrary kernel memory access.

Technical ContextAI

The vulnerability resides in drivers/firewire/net.c within the Linux kernel's IEEE 1394 (FireWire) networking subsystem, present since version 2.6.31. The fwnet_frag_new() function maintains a sorted doubly-linked list of received datagram fragment ranges to track reassembly progress for each partial datagram. The defect is a dual boundary-condition error: first, when checking whether a newly inserted fragment is adjacent to its neighbors, the code does not guard against the neighboring entry being the list head (struct list_head) rather than a real struct fwnet_fragment_info - dereferencing the list head as if it were a fragment structure constitutes type confusion that can corrupt kernel memory. Second, the adjacency gap comparison uses the original fragment edge rather than the edge after the new fragment is merged in, so a single incoming fragment that bridges two pre-existing ranges may leave those ranges unmerged. The downstream effect is that fwnet_pd_is_complete() may fail to recognize a fully received datagram, producing resource leaks or, in the type-confusion path, kernel-level memory safety violations. CWE is not formally assigned, but the root cause maps to improper linked-list boundary checking (analogous to CWE-754). Affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* from 2.6.31 through the patched stable releases.

RemediationAI

Upgrade to a patched stable kernel release: 6.6.148 or later for the 6.6 LTS branch, 6.12.101 or later for 6.12 LTS, 6.18.42 or later for 6.18, or 7.1.6 or later for 7.1; all five fix commits are available at git.kernel.org/stable as referenced in the CVE. Distribution maintainers for Debian, Ubuntu, Red Hat, SUSE, and others should be monitored for backported stable packages. Where immediate kernel upgrade is not feasible, the most effective compensating control is unloading the firewire-net module (modprobe -r firewire-net) and blacklisting it (echo 'blacklist firewire_net' >> /etc/modprobe.d/blacklist.conf) to eliminate the attack surface entirely; the only side effect is loss of IEEE 1394 networking functionality, which is unused in the vast majority of deployments. Systems without FireWire ports or with firewire-net absent from lsmod output are not exposed and require no action beyond confirming module absence.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-55455 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy