[CVE-2026-80897][LOW] netfs: release readahead folios on iterator preparation failure [ Upstream

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

CVE: CVE-2026-80897
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: netfs: release readahead folios on iterator preparation failure [ Upstream
Commit: 2c148a31ca01fc160aceec777bbc0041b0d0b8bd
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c148a31ca01fc160aceec777bbc0041b0d0b8bd
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80897
Analysis date: Fri, 04 Sep 2026 15:00:21 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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: LOW
Manual review required: NO

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

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

CVE-2026-80897	LOW	https://www.kernelcve.org/list/?q=CVE-2026-80897 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-772;*CWE-401;**CWE-400;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A reference leak in the netfs buffered read path can occur when netfs_prepare_read_iterator returns immediately after rolling_buffer_load_from_ra fails, leaving previously batched readahead folios unreleased. This may pin folios and gradually consume memory or page cache resources if the failure path can be triggered repeatedly. For the CVSS the PR:L is used because a local user or process with access to a netfs backed file can initiate reads, while reliable triggering still depends on an iterator preparation failure and therefore has high complexity. The issue is not directly network reachable as a packet driven attack, although it is relevant to network filesystem clients and may depend on backend or server induced I/O error conditions. Impact is denial of service through resource exhaustion only, with no evidence of memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)  SKIP CVE-2026-80897 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	REMOTE DISK SIMPLEFIX LINUS  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

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

ActionableScore=2
ActionableScoreLower=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate**::

No floor or cap changed the score.

2. Signal breakdown

Conservative positive signals:

* +1 Concrete persistent kernel resource/reference leak. The patch directly shows that folio references accumulated in put_batch are not released when rolling_buffer_load_from_ra() returns an error before the normal folio_batch_release() path.

Conservative negative signals:

* No negative privilege penalty. Host-admin-equivalent privilege is not established for the runtime read path once the netfs mount exists.
* No race/timing penalty. This is an ordered error-path leak, not a timing race.

Paranoid additional signal:

* +1 Possible sustained resource pressure. If the failing iterator preparation path can be triggered repeatedly, unreleased folio references may accumulate and cause memory or page-cache resource pressure.

Important non-awarded signals:

* RealUAF not awarded. The bug leaves references held, but does not use an object after its lifetime ends.
* Concrete repeated release/refcount not awarded. There is no first release that may free an object followed by a second put/release on the exact same dangling reference.
* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Confidentiality and integrity impact not awarded. The patch supports a reference leak only, not information disclosure or unauthorized modification.
* Reliable kernel crash not awarded. The commit describes leaked references, not an immediate panic or deterministic host crash.
* Remote reachability not awarded. This is a client-side netfs read path and not a packet-driven remote kernel attack.
* Extra availability point is only used in the paranoid score for sustained accumulation, not for an immediate crash.

Repeated-release/refcount check:

* First release can end lifetime: not applicable.
* Exact same reference survives for second lifetime mutation: not established.
* Second operation is a real lifetime/refcount mutation: not established.
* Concrete repeated release/refcount +1 awarded: no.
* Paranoid repeated-refcount leverage +1 awarded: no.
* FLOOR 5 applied: no.

3. Reachability analysis

A local process that can read from a netfs-backed file can enter the affected buffered read path. The complete leak also depends on rolling_buffer_load_from_ra() failing after some readahead folios were already batched, so the attacker does not fully control all trigger conditions from the supplied patch alone.

Host administrator privileges are not positively required for the runtime read operation, assuming the filesystem is already mounted and accessible according to normal file permissions. Prior privileged setup may exist in practice because netfs-backed filesystems are mounted or provisioned by an administrator, but that is deployment setup rather than proof that the vulnerable runtime path itself requires host-admin-equivalent privilege.

No namespace-scoped capability requirement is involved. No special hardware is indicated. No race is involved. A remote server or backend error condition could contribute to the failure path, but the supplied evidence does not establish direct remote packet reachability against the kernel client.

4. Primitive and severity interpretation

The exact primitive is a missing folio_batch_release() on an error return path, causing a persistent folio reference leak. This is a resource/lifetime accounting defect, not a use-after-free and not a double release.

The affected objects are readahead folios whose references remain held longer than intended. The stale state is fixed retained storage rather than attacker-controlled reclaimed memory. The demonstrated consequence is resource leakage and possible memory pressure if repeated. The speculative consequence is broader denial of service through accumulated pinned folios, but no patch-supported path shows memory corruption, privilege escalation, arbitrary read/write, or disclosure.

PrimitiveClass is CLASS_C because the demonstrated behavior is resource-leak DoS style behavior without an independently useful corruption primitive. ImportantCandidate is NO because there is no UAF, no repeated lifetime mutation, no security-boundary bypass, and no controlled corruption. AutoDowngradeAllowed is YES because unresolved Important-grade exploitation leverage is not present.

Likely operational severity is Low to ordinary Moderate.

5. One-sentence report phrase

A netfs buffered read error path can leak references to batched readahead folios when iterator preparation fails, which may allow local resource exhaustion if the failure path is repeatedly triggered.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a constrained reference leak with no evidence of UAF, double release, memory corruption, information disclosure, privilege escalation, or security-boundary bypass.

7. Call-site confidence

Call-site confidence: medium

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

Patch: netfs: release readahead folios on iterator preparation failure [ Upstream
Commit: 2c148a31ca01fc160aceec777bbc0041b0d0b8bd
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c148a31ca01fc160aceec777bbc0041b0d0b8bd

Changed files:
  fs/netfs/buffered_read.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=2c148a31ca01fc160aceec777bbc0041b0d0b8bd

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

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

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

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

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: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

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