[CVE-2026-72378][MODERATE REGULAR] afs: Fix error code in afs_extract_vl_addrs() [ Upstream

[CVE-2026-72378][MODERATE REGULAR] afs: Fix error code in afs_extract_vl_addrs() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72378
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: afs: Fix error code in afs_extract_vl_addrs() [ Upstream
Commit: 7ce6737a975ea3e0dc2e5946628d233779ca0caf
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7ce6737a975ea3e0dc2e5946628d233779ca0caf
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72378
Analysis date: Sun, 16 Aug 2026 01:16:03 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline Moderate, manual review recommended
Manual review required: YES

Summary:
A malformed AFS VL address response can make `afs_extract_vl_addrs()` return an incorrect error status after later loop iterations, potentially causing failed client operations or caller confusion, but no concrete memory corruption primitive is demonstrated.

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

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

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-72378	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:R/S:U/C:N/I:N/A:H';CWE-393;CWE-703;*CWE-20;Other CVSS 'AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L';BEST CVSS score: '5.3';DESCR 'afs_extract_vl_addrs can return an incorrect error status when a malformed IPv4 or IPv6 VL address is encountered after the first loop iteration. This is caused by stale ret handling during network supplied address list parsing and can make the caller observe success or a wrong error after a parse failure. For the CVSS the PR:N is used because attacker privileges on the victim are not required if the client contacts a malicious or compromised AFS related service. UI:R is used because the victim client must perform an AFS lookup or mount related operation that reaches the malformed response. Impact is mainly denial of service or failed AFS operation. There is no clear memory corruption primitive in the patch, but the wrong success or error return path should be checked for possible NULL pointer or ERR_PTR misuse in callers.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate, manual review recommended (with actual score 4)	YES	DISK SIMPLEFIX SKIP IPV6  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline Moderate, manual review recommended**::

## 2. Signal breakdown

Conservative signals:

* Remote reachable / network-triggerable: +2
  The malformed VL address data can plausibly come from a malicious or compromised AFS related service contacted by the client.

* Availability impact realistic: +1
  Incorrect error propagation can cause failed AFS lookup or mount behavior, and may affect client operation.

* Rare AND difficult-to-reach subsystem/configuration: -1
  AFS is not a broad default deployment path on most systems.

* Weak return-value consequence concern: +1
  The helper returns a pointer-like result where wrong `ret` handling may cause callers to observe success or an unexpected error object after parse failure.

Paranoid delta:

* Possible NULL or ERR_PTR misuse in callers: +1
  If stale `ret` becomes 0 or otherwise incorrect, caller handling should be checked for NULL, ERR_PTR, or partially initialized object assumptions.

No strong signals:

* No demonstrated UAF, OOB write, double free, refcount takeover, type confusion, arbitrary write, or page-cache corruption.
* No direct privilege escalation evidence.
* No strong DoS evidence such as shown kernel panic or reliable host crash.

## 3. Reachability analysis

An attacker would typically need to influence the AFS VL address response seen by a victim client, for example through a malicious or compromised AFS related service or network position. The victim likely needs to perform an AFS lookup, mount, or similar operation, so practical triggering is not fully automatic. No local privileges on the victim are needed in the network-response model, but the affected subsystem is uncommon and usually not enabled or used by default. Namespaces and containers do not materially lower the trigger requirement unless they can cause the host or container kernel AFS client to contact attacker-controlled AFS infrastructure.

Call-site confidence: medium. The patch shows the parser and return-code fix, but not all callers or the exact error label behavior.

## 4. Severity interpretation

This behaves more like a low-to-borderline Moderate network-influenced parser error than an Important kernel vulnerability. The realistic impact is failed AFS operation or possible DoS in a specific AFS client workflow. Theoretical caller misuse could raise concern, but the patch does not show a concrete memory corruption primitive or a demonstrated privilege escalation path.

## 5. One-sentence report phrase

A malformed AFS VL address response can make `afs_extract_vl_addrs()` return an incorrect error status after later loop iterations, potentially causing failed client operations or caller confusion, but no concrete memory corruption primitive is demonstrated.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: network-influenced parser error handling plus pointer-like return semantics should be checked in callers for NULL or ERR_PTR misuse, but current evidence does not justify Important-class handling.

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

Patch: afs: Fix error code in afs_extract_vl_addrs() [ Upstream
Commit: 7ce6737a975ea3e0dc2e5946628d233779ca0caf
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7ce6737a975ea3e0dc2e5946628d233779ca0caf

Changed files:
  fs/afs/vl_list.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=7ce6737a975ea3e0dc2e5946628d233779ca0caf

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

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

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

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: 4

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