[CVE-2026-72377][MODERATE REGULAR] afs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72377
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: afs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints [ Upstream
Commit: 9d6b0f6d437e2f8350e08678e5e1d20c11c364f3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9d6b0f6d437e2f8350e08678e5e1d20c11c364f3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72377
Analysis date: Sun, 16 Aug 2026 08:13:35 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline manual review recommended / Actionable Moderate watchlist
Manual review required: YES

Summary:
AFS symlinks and mountpoints could incorrectly reach the folio release path with AS_RELEASE_ALWAYS set but without a release_folio callback, allowing a local user or malicious AFS server in a mounted deployment to trigger a NULL pointer dereference and kernel DoS.

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

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

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-72377	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-476;CWE-703;*CWE-664;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'AFS symlinks and mountpoints can reach the folio release path with AS_RELEASE_ALWAYS set even though their address_space_operations do not provide a release_folio callback. When filemap_release_folio() sees that release is required, it can fall through to try_to_free_buffers() on folios that have no buffer_heads, causing a NULL pointer dereference and kernel crash. For the CVSS the PR:N is used in the paranoid server controlled scenario because a malicious or compromised AFS server does not need an account on the client, but practical triggering still requires the client to mount and access affected AFS objects. The issue is network influenced through AFS content but is not a generic unauthenticated packet parsing bug. Impact is denial of service via kernel crash, with no clear evidence of information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / Actionable Moderate watchlist (with actual score 4)  SKIP CVE-2026-72377 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: eae9e78951bb02a7b94a9adef6e981413d13c564 YES  NO NO unknown 	MAYBE	DISK INIT SIMPLEFIX SKIP IMPROVEONLY LINUS  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	-	-	checked

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

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline manual review recommended / Actionable Moderate watchlist**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1
  A local user may be able to access AFS symlinks or mountpoints through an already mounted AFS filesystem.

* Reliable kernel crash / strong DoS: +1
  The described failure is a NULL pointer dereference in the folio release path, leading to kernel crash or Oops.

* Important filesystem/storage path: +1
  The bug is in AFS plus netfs plus folio release behavior, which is a filesystem and memory-management interaction.

Paranoid additional / adjusted signals:

* Remote reachable / network-influenced filesystem content: +2
  A malicious or compromised AFS server may influence the inode type and filesystem objects exposed to the client. This is not a generic unauthenticated packet parser bug, but the vulnerable client behavior can be influenced by network-provided AFS content.

* Rare / configuration-dependent exposure: -1
  AFS is not commonly enabled or mounted by default in typical deployments, and exploitation depends on AFS being in use.

Not awarded:

* Generic memory corruption: +0
  The patch supports a NULL pointer dereference, not UAF, OOB write, double free, type confusion, or attacker-controlled overwrite.

* Privilege escalation plausible: +0
  No reclaim, stale object reuse, writable freed object, callback control, or arbitrary write primitive is shown.

* Confidentiality / Integrity impact: +0
  The supported impact is availability only.

## 3. Reachability analysis

A local user can plausibly trigger the affected path by accessing AFS symlinks or mountpoints on a system where AFS is mounted. A remote attacker cannot generally trigger this against arbitrary hosts, but a malicious or compromised AFS server can influence filesystem objects delivered to a client that mounts and accesses that server. Namespaces do not substantially improve reachability unless the container or namespace has access to the host AFS mount. The path is not default-enabled on most systems because AFS usage is deployment-specific.

## 4. Severity interpretation

This behaves like a borderline actionable Moderate issue, not a strong Important candidate. The realistic impact is kernel crash or local DoS through a NULL pointer dereference. Theoretical escalation is not well supported because the patch does not show UAF, object reuse, write-after-free, OOB write, refcount takeover, or callback corruption. Manual review is still useful because the bug is in a network-backed filesystem client path and server-controlled filesystem metadata may affect triggerability.

## 5. One-sentence report phrase

AFS symlinks and mountpoints could incorrectly reach the folio release path with AS_RELEASE_ALWAYS set but without a release_folio callback, allowing a local user or malicious AFS server in a mounted deployment to trigger a NULL pointer dereference and kernel DoS.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED. YES REQUIRES MANUAL CHECK.

Reason: the confirmed primitive is only NULL pointer dereference and DoS, but the bug is network-influenced through AFS server-provided filesystem objects, so exposure and triggerability should be verified against actual product configuration.

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

Patch: afs: Remove setting of AS_RELEASE_ALWAYS for symlinks and mountpoints [ Upstream
Commit: 9d6b0f6d437e2f8350e08678e5e1d20c11c364f3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9d6b0f6d437e2f8350e08678e5e1d20c11c364f3

Changed files:
  fs/afs/inode.c
  fs/afs/internal.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=9d6b0f6d437e2f8350e08678e5e1d20c11c364f3

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

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

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:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  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).