[CVE-2026-68168][MODERATE 7.0] afs: Fix afs_edit_dir_remove() to get, not find, block 0

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

CVE: CVE-2026-68168
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: afs: Fix afs_edit_dir_remove() to get, not find, block 0
Commit: f2b293359924117736218701ebd8b40618d73e6f
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f2b293359924117736218701ebd8b40618d73e6f
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68168
Analysis date: Mon, 10 Aug 2026 19:23:04 -0400
ActionableScore: 5
ActionableScore lower bound: 3
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
AFS directory removal used a block lookup helper that can cache iterator state and switch the backing page, potentially leaving an unsafe metadata block pointer during directory entry removal and causing filesystem metadata corruption or client-side DoS.

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

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

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-68168	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:L/I:L/A:H';*CWE-672;*CWE-664;*CWE-416;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '6.4';DESCR 'afs_edit_dir_remove used afs_dir_find_block to obtain directory block 0 even though that helper caches the found block in afs_dir_iter and can switch the backing page during later block searches. This can leave the metadata block pointer in an unsafe or stale state while removing an AFS directory entry, which makes the bug a stale pointer and possible use-after-free candidate rather than a simple logic issue. For the CVSS the PR:N is used in the paranoid network server scenario because an attacker may only need control of a malicious or compromised AFS server while the victim client performs the directory operation. The issue is not directly triggered by arbitrary Internet packets and usually depends on AFS client activity against a crafted or controlled directory. Impact is at least integrity risk for directory state and availability impact. In the worst still defensible case it may allow limited confidentiality or integrity impact due to stale pointer behavior and should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)  SKIP CVE-2026-68168 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: a5b5beebcf96d5e8a2fc79856c2ac1e93f82478e YES  NO NO unknown 	MAYBE	DISK SIMPLEFIX SKIP LINUS  INCREASED_TO_MODERATE_FROM_LOW_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	-	-	checked

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

ActionableScore=5
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged trigger: +1. A local user with access to an AFS mount may trigger directory removal operations without needing full host root.
* Memory corruption, weak/indirect corruption candidate: +1. The wrong helper can cache block state in `afs_dir_iter` and later switch the backing page, making the saved block 0 metadata pointer potentially stale or unsafe.
* Filesystem/storage metadata corruption reachable by an unprivileged local user: +1. The affected path edits AFS directory metadata during remove operations.
* Integrity impact plausible: +1. Incorrect directory metadata editing can plausibly corrupt local AFS directory state or cache-visible filesystem state.
* Rare/configuration-dependent subsystem: -1. AFS is not a default/common filesystem on most Linux systems.

Paranoid additional interpretation:

* Remote/network-filesystem server influence: +2. A malicious or compromised AFS server may influence directory layout and metadata seen by the client, although this is not arbitrary Internet packet reachability.
* Real lifetime/stale pointer concern: +1. The commit explicitly mentions cached block state and possible page switching, which makes this more concerning than simple bookkeeping.
* Availability impact realistic: +1. Bad directory metadata handling or stale pointer use could plausibly lead to client-side failure or kernel crash, although this is not demonstrated in the patch.
* Hard or unreliable triggering: -1. Exploitation depends on directory layout, multiple blocks per page, and the exact iterator behavior.
* Constrained/uncertain primitive: -1. No attacker-controlled overwrite, reclaim, type confusion, or callback control is shown.

Call-site confidence: medium. The changed function is directly a directory remove helper, but the patch snippet does not include all callers or full iterator lifetime code.

## 3. Reachability analysis

The conservative trigger is local file operation activity on an already mounted AFS filesystem. This generally does not require full root if the user has normal permissions on the AFS directory. Mount setup itself is usually administrative, but the vulnerable operation can be reached after the mount exists.

The paranoid scenario involves a malicious or compromised AFS server shaping directory contents or layout while a victim client performs directory operations. This is network-influenced but not a fully unauthenticated remote packet path. Namespaces do not significantly reduce the concern if the AFS mount is exposed inside the namespace or container.

AFS is relatively uncommon and not default-enabled for most deployments, so broad exposure is limited.

## 4. Severity interpretation

This is not an ordinary low-risk cleanup because the patch changes a helper used to obtain directory block 0 in a metadata editing path, and the commit explicitly explains that the old helper caches iterator state and may switch the backing page. That creates a plausible stale pointer or UAF-like concern.

Realistic evidence supports Actionable Moderate rather than Important. There is no demonstrated arbitrary write, controlled reclaim, type confusion, or privilege escalation primitive. The paranoid score is higher because network filesystem metadata is externally influenced and stale metadata pointers in filesystem edit paths deserve manual review.

## 5. One-sentence report phrase

AFS directory removal used a block lookup helper that can cache iterator state and switch the backing page, potentially leaving an unsafe metadata block pointer during directory entry removal and causing filesystem metadata corruption or client-side DoS.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch is small but touches filesystem metadata editing and explicitly describes cached iterator state with possible page switching, which makes this a stale pointer or UAF candidate rather than a simple correctness fix.

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

Patch: afs: Fix afs_edit_dir_remove() to get, not find, block 0
Commit: f2b293359924117736218701ebd8b40618d73e6f
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f2b293359924117736218701ebd8b40618d73e6f

Commit description:

Fix afs_edit_dir_remove() to use afs_dir_get_block() to get block 0 rather
than afs_dir_find_block() as the latter caches the found block in the
afs_dir_iter and may[*] switch out the page it's on if another
afs_dir_find_block() is done.  This parallels what afs_edit_dir_add() does.

[*] There's more than one block per page.

Fixes: a5b5bee ("afs: Use the contained hashtable to search a directory")
Closes: https://sashiko.dev/#/patchset/20260706153408.1231650-1-dhowells%40redhat.com
Signed-off-by: David Howells <dhowells@redhat.com>
Link: https://patch.msgid.link/2380759.1783956175@warthog.procyon.org.uk
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
cc: linux-fsdevel@vger.kernel.org
cc: stable@vger.kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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

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

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

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

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

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