[CVE-2026-68354][MODERATE 7.0] firewire: net: Fix fragmented datagram reassembly [ Upstream

[CVE-2026-68354][MODERATE 7.0] firewire: net: Fix fragmented datagram reassembly [ Upstream

[AL-KERNEL]

CVE: CVE-2026-68354
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: firewire: net: Fix fragmented datagram reassembly [ Upstream
Commit: b7d633c7c92321be98724b1d365e8ce507f2f349
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7d633c7c92321be98724b1d365e8ce507f2f349
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68354
Analysis date: Mon, 10 Aug 2026 18:49:56 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
FireWire network fragmented datagram reassembly can treat a list edge as a real fragment object during gap merging, allowing an adjacent FireWire peer to trigger failed reassembly and potentially invalid list or free operations leading to DoS or limited kernel memory corruption concern.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68354 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68354

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-68354	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';CWE-125;*CWE-787;CWE-590;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.4';DESCR 'FireWire network fragmented datagram reassembly can inspect a list edge as if it were a real fwnet_fragment_info object. A peer on the same FireWire bus may be able to trigger invalid reads or list manipulation during fragment insertion, and a complete datagram can also be missed when adjacent ranges are not merged correctly. For the CVSS the PR:N is used because the attacker does not need local code execution on the victim once FireWire network traffic from the adjacent bus is accepted. The issue is not Internet routable and should be treated as adjacent network exposure rather than normal IP remote exposure. Impact is at least denial of service through broken reassembly or kernel failure. In the paranoid case, limited confidentiality or integrity impact is kept because the list head can be treated as a fragment object and this is a plausible memory corruption candidate, but a reliable privilege escalation primitive is not proven from the patch alone.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	NETWORK LINUS  LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Network-triggerable adjacent exposure: +2. The affected path processes FireWire networking fragments from a peer on the same FireWire bus, so this is not Internet remote, but it is externally triggerable over an adjacent network medium.
* Memory corruption, weak/indirect corruption candidate: +1. The old code can treat the list head as a `struct fwnet_fragment_info`, which is bogus struct interpretation.
* Reliable kernel crash / strong DoS: +1. If the bogus neighbor comparison matches, the code may reach `list_del()` and `kfree()` on an object that is not a real fragment. Even without that, reassembly can fail.
* Hard or special fragment arrangement required: -1. Triggering the dangerous edge case requires specific fragmented datagram layout and list-edge adjacency.
* Physical-only or rare hardware-only condition: -2. FireWire networking is uncommon and requires access to the same FireWire bus.

Paranoid additional signals:

* Weak LPE concern: +1. The bug has an invalid object interpretation and possible corruption sink through list manipulation or invalid free, but no demonstrated reclaim, callback control, arbitrary write, or type confusion.
* Real lifetime corruption candidate: +1. The code path may free a pointer derived from the list head instead of a real allocated fragment object.
* Confidentiality impact plausible: +1. Kept only in the paranoid score because bogus struct interpretation can read fields from the surrounding object layout, but no user-visible disclosure primitive is demonstrated.
* Integrity impact plausible: +1. Kept only in the paranoid score because `list_del()` or `kfree()` on a non-fragment object can corrupt kernel list or allocator state, but the target and payload are not controlled.

## 3. Reachability analysis

A peer capable of sending FireWire network traffic on the same FireWire bus may influence fragmented datagram reassembly. No local credentials on the victim are required once FireWire networking traffic is accepted, so the practical privilege interpretation is PR:N for CVSS-style reasoning, but the attack surface is adjacent and hardware-dependent rather than Internet-routable.

Namespaces and containers do not meaningfully expand reachability unless they can access the FireWire networking interface. The path is not broadly default-exposed on typical servers because FireWire hardware and fwnet use are uncommon. Realistic exploitation requires a FireWire networking deployment and carefully shaped fragmented datagrams.

Call-site confidence: high for the local corruption concern because the patch shows the neighbor lookup, `list_del()`, and `kfree()` behavior directly. Medium for exploitability because the broader packet injection and exact matching conditions are not fully shown in the provided context.

## 4. Severity interpretation

This is stronger than an ordinary Moderate logic bug because the old code can interpret a list head as a fragment object and may reach list manipulation or invalid free paths. It is not a Strong Important candidate on the available evidence because there is no demonstrated attacker-controlled reclaim, overwrite payload, arbitrary write, callback dispatch, or practical privilege-escalation chain.

Conservatively it behaves like a rare adjacent-network DoS or corruption candidate. Paranoid handling should keep it as Actionable Moderate because the memory-corruption shape is real enough to require manual source review.

## 5. One-sentence report phrase

FireWire network fragmented datagram reassembly can treat a list edge as a real fragment object during gap merging, allowing an adjacent FireWire peer to trigger failed reassembly and potentially invalid list or free operations leading to DoS or limited kernel memory corruption concern.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

The bug is adjacent-network reachable in affected FireWire networking setups and the patch fixes bogus object interpretation near `list_del()` and `kfree()` paths, so it should not be auto-closed despite rare hardware exposure.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: firewire: net: Fix fragmented datagram reassembly [ Upstream
Commit: b7d633c7c92321be98724b1d365e8ce507f2f349
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7d633c7c92321be98724b1d365e8ce507f2f349

Changed files:
  drivers/firewire/net.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7d633c7c92321be98724b1d365e8ce507f2f349

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68354 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68354

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 6.4

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 3
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).