[CVE-2026-72374][MODERATE REGULAR] afs: Fix callback service message parsers to pass through -EAGAIN [ Upstream

[CVE-2026-72374][MODERATE REGULAR] afs: Fix callback service message parsers to pass through -EAGAIN [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72374
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: afs: Fix callback service message parsers to pass through -EAGAIN [ Upstream
Commit: 26b737b3769e92493fe94c34620399d93ca231ae
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=26b737b3769e92493fe94c34620399d93ca231ae
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72374
Analysis date: Sat, 15 Aug 2026 22:38:40 -0400
ActionableScore: 3
ActionableScore lower bound: 2
Actionable bucket: Ordinary Moderate / Borderline manual review recommended
Manual review required: YES

Summary:
AFS RXRPC callback parsers incorrectly converted `-EAGAIN` from incomplete request extraction into success, allowing a malicious callback peer to cause protocol state confusion and potential AFS client denial of service.

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

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

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 REGULAR
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-72374	MODERATE	CHECK WITH IMPACT FROM ORIG NN NONE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-703;CWE-754;CWE-755;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.9';DESCR 'AFS/RXRPC callback service parsers can incorrectly treat an incomplete request stream as successfully consumed because -EAGAIN from afs_extract_data was converted to 0 in selected handlers. A remote peer in the AFS callback path, typically a malicious or compromised AFS fileserver or an attacker able to tamper with that traffic, can trigger protocol state confusion by sending partial callback messages where queued data is consumed but the final packet has not arrived. For the CVSS the PR:N is used because no privileges on the victim host are required once the attacker can reach or impersonate the relevant AFS callback peer. The issue is network reachable but exposure is usually limited to systems using AFS and to servers or networks trusted by the AFS client. Impact is primarily denial of service or loss of correct callback processing for AFS client state, with no concrete evidence of memory corruption or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Borderline manual review recommended (with actual score 3)  SKIP CVE-2026-72374 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: d001648ec7cf8b21ae9eec8b9ba4a18295adfb14 YES  NO NO unknown 	MAYBE	DANGER DISK SKIP LINUS PACKET  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=3
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 3
* Final recommended bucket: **Ordinary Moderate / Borderline manual review recommended**::

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2
  AFS callback handling is reached through RXRPC network callback messages from an AFS fileserver or a peer able to interfere with that traffic.
* Availability impact realistic: +1
  Incorrectly converting `-EAGAIN` to success can cause incomplete callback messages to be processed with wrong parser state, plausibly disrupting AFS callback handling.
* Rare AND difficult-to-reach subsystem/configuration: -1
  AFS client callback service is not a broadly exposed default Internet-facing path and normally matters only on systems using AFS.

Conservative total: 2

Paranoid additional interpretation:

* Reliable kernel crash / strong DoS: +1
  Not proven by the patch, but defensible as a paranoid signal because protocol state confusion in an in-kernel filesystem callback parser may lead to stuck calls or stronger client-side DoS.

Paranoid total: 3

Not awarded:

* No generic memory corruption signal. The patch shows error propagation in parser delivery functions, not UAF, OOB write, double-free, refcount misuse, or type confusion.
* No privilege escalation signal. There is no concrete reclaim, overwrite, callback hijack, or security-boundary bypass primitive.
* No confidentiality or integrity signal. The supported impact is callback state mishandling and availability degradation.

## 3. Reachability analysis

The bug can be triggered by a remote peer that participates in the AFS callback path, typically a malicious or compromised AFS fileserver or an attacker able to tamper with RXRPC traffic. No local privileges on the victim are required once that network position exists, so the practical CVSS-style PR interpretation is PR:N. The path is not generally exposed on default systems and requires AFS client usage. Containers and namespaces do not materially lower the trigger requirement unless the containerized workload can cause the host to use AFS and interact with attacker-controlled AFS infrastructure.

Call-site confidence: high. The patch directly shows the affected callback delivery handlers and the commit message describes the intended `-EAGAIN` parser contract.

## 4. Severity interpretation

This behaves more like an ordinary Moderate issue with manual-review relevance than an Important-class kernel vulnerability. The theoretical concern is that an in-kernel network parser enters an invalid state after partial message delivery, but the patch does not support memory corruption or privilege escalation. Realistic impact is AFS client callback malfunction or DoS under a specific network/filesystem deployment.

## 5. One-sentence report phrase

AFS RXRPC callback parsers incorrectly converted `-EAGAIN` from incomplete request extraction into success, allowing a malicious callback peer to cause protocol state confusion and potential AFS client denial of service.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the issue is network-triggerable in an in-kernel filesystem protocol parser, even though the current evidence supports DoS/state-confusion only and not memory corruption or privilege escalation.

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

Patch: afs: Fix callback service message parsers to pass through -EAGAIN [ Upstream
Commit: 26b737b3769e92493fe94c34620399d93ca231ae
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=26b737b3769e92493fe94c34620399d93ca231ae

Changed files:
  fs/afs/cmservice.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=26b737b3769e92493fe94c34620399d93ca231ae

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

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

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

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: 2
  Paranoid ActionableScore: 3

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 REGULAR

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