[CVE-2026-72351][MODERATE 7.0] gue: validate REMCSUM private option length [ Upstream

[CVE-2026-72351][MODERATE 7.0] gue: validate REMCSUM private option length [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72351
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: gue: validate REMCSUM private option length [ Upstream
Commit: 158b9995d3c87f3b93f5c22df54a12e12a3438b3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=158b9995d3c87f3b93f5c22df54a12e12a3438b3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72351
Analysis date: Sat, 15 Aug 2026 23:43:40 -0400
ActionableScore: 6
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A malformed GUE packet with REMCSUM private flags can bypass option length validation and cause `gue_remcsum()` or `gue_gro_remcsum()` to read missing REMCSUM fields from following bytes, making this a remotely triggerable invalid read candidate with DoS and limited C/I concern when GUE is exposed.

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

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

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-72351	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H';*CWE-20;CWE-125;CWE-754;Other CVSS 'AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L';BEST CVSS score: '8.6';DESCR 'A malformed GUE packet with GUE_PFLAG_REMCSUM can pass option validation even when the REMCSUM start and offset fields are missing. Later gue_remcsum or gue_gro_remcsum may read those missing fields from following bytes, which makes this a network input validation bug with an out-of-bounds read candidate in the GUE receive path. For the CVSS the PR:N because a remote sender does not need local privileges on the target when the GUE endpoint is reachable. The issue is network reachable only on systems that use GUE and expose the relevant encapsulation endpoint. Impact is at least denial of service or incorrect packet processing, and the paranoid score keeps C:L/I:L/A:H because a network reachable invalid read should be reviewed manually even without a proven write primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-72351 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE SIMPLEFIX LINUS KPANIC PACKET  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN6	-	-	checked

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

ActionableScore=6
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 6
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2. A malformed GUE packet can trigger the affected validation path if a GUE endpoint is reachable.
* Memory corruption, weak/indirect corruption candidate: +1. The patch prevents reading missing REMCSUM start/offset fields from following bytes. This is an invalid/OOB read candidate, not a write primitive.
* Availability impact realistic: +1. Malformed packet parsing can plausibly cause packet-processing failure, warning, crash, or DoS depending on skb layout and build/debug conditions.
* Common networking packet-processing path: +1. This is in the network receive/GRO parsing path for GUE encapsulation.
* Rare/configuration-dependent exposure: -1. GUE is not a universally exposed default Internet-facing protocol and normally requires a configured encapsulation endpoint.

Paranoid additional signals:

* Confidentiality impact plausible: +1. The invalid read may consume bytes outside the expected option structure, so limited information misuse/disclosure concern is defensible for manual review, although no direct leak is demonstrated.
* Integrity impact plausible: +1. Incorrect REMCSUM metadata parsing may affect checksum handling or packet processing decisions, but no write primitive is shown.

Not awarded:

* No strong memory corruption +2. The patch shows missing length accounting and invalid read, not UAF, double-free, OOB write, heap overwrite, or arbitrary write.
* No LPE bonus. There is no reclaim, controlled overwrite, callback control, refcount takeover, or type confusion.
* No Dirty-Pipe-like or page-cache ownership violation.

## 3. Reachability analysis

A remote sender can potentially trigger this by sending a malformed GUE packet with `GUE_PFLAG_REMCSUM` set but without the required REMCSUM metadata fields. No local privileges are needed on the target in the network-reachable case. However, practical exposure depends on whether GUE is enabled and whether the relevant tunnel or encapsulation endpoint is reachable from an untrusted network. This is not a generic TCP/IP core bug exposed on every host by default.

Namespaces and containers do not substantially change the remote interpretation. For local/containerized attackers, reachability depends on whether they can inject packets toward a configured GUE endpoint.

Call-site confidence: medium. The commit explicitly names `validate_gue_flags()`, `gue_remcsum()`, and `gue_gro_remcsum()`, but the full caller context is not included in the pasted patch.

## 4. Severity interpretation

This is more than an ordinary Moderate because it is a network-reachable packet parser validation bug with an invalid/OOB read candidate. It should not be auto-closed without review.

It does not reach a strong Important classification on the supplied evidence because the primitive is read-only and there is no demonstrated memory write, UAF, object lifetime corruption, privilege escalation path, or arbitrary kernel memory access. The paranoid score is elevated to Actionable Moderate because network parser bugs with malformed option length handling are historically easy to underestimate.

## 5. One-sentence report phrase

A malformed GUE packet with REMCSUM private flags can bypass option length validation and cause `gue_remcsum()` or `gue_gro_remcsum()` to read missing REMCSUM fields from following bytes, making this a remotely triggerable invalid read candidate with DoS and limited C/I concern when GUE is exposed.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED.

YES REQUIRES MANUAL CHECK.

Reason: network-reachable malformed packet parsing plus an invalid/OOB read candidate is enough to require manual review, even though the patch does not show a strong write primitive or confirmed privilege escalation.

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

Patch: gue: validate REMCSUM private option length [ Upstream
Commit: 158b9995d3c87f3b93f5c22df54a12e12a3438b3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=158b9995d3c87f3b93f5c22df54a12e12a3438b3

Changed files:
  include/net/gue.h

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=158b9995d3c87f3b93f5c22df54a12e12a3438b3

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

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

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:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
  The Best / paranoid CVSS vector: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 8.6

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: 4
  Paranoid ActionableScore: 6

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: YES
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).