From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68168: afs: Fix afs_edit_dir_remove() to get, not find, block 0
Date: Mon, 10 Aug 2026 13:58:05 +0200 [thread overview]
Message-ID: <2026081005-CVE-2026-68168-38e8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix afs_edit_dir_remove() to get, not find, block 0
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.
The Linux kernel CVE team has assigned CVE-2026-68168 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit a5b5beebcf96d5e8a2fc79856c2ac1e93f82478e and fixed in 6.18.42 with commit f2b293359924117736218701ebd8b40618d73e6f
Issue introduced in 6.14 with commit a5b5beebcf96d5e8a2fc79856c2ac1e93f82478e and fixed in 7.1.6 with commit bfdfc7782ada6f3a4df7182889b66039f8e4131c
Issue introduced in 6.14 with commit a5b5beebcf96d5e8a2fc79856c2ac1e93f82478e and fixed in 7.2-rc5 with commit 62d9853aa4ce6e9797b6949804891be14b219752
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-68168
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/afs/dir_edit.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/f2b293359924117736218701ebd8b40618d73e6f
https://git.kernel.org/stable/c/bfdfc7782ada6f3a4df7182889b66039f8e4131c
https://git.kernel.org/stable/c/62d9853aa4ce6e9797b6949804891be14b219752
reply other threads:[~2026-08-10 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081005-CVE-2026-68168-38e8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.