From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72373: afs: Fix missing NULL pointer check in afs_break_some_callbacks()
Date: Sat, 15 Aug 2026 15:07:32 +0900 [thread overview]
Message-ID: <2026081516-CVE-2026-72373-c10b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix missing NULL pointer check in afs_break_some_callbacks()
Fix afs_break_some_callbacks() to check to see if afs_lookup_volume_rcu()
returned NULL (e.g. the specified volume is unknown).
The Linux kernel CVE team has assigned CVE-2026-72373 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.8 with commit 8230fd8217b7ea76f838ae88e4a5a8e54f37099f and fixed in 6.12.97 with commit a99a617701186dc68c7b330d35fc2253f48e2ab2
Issue introduced in 5.8 with commit 8230fd8217b7ea76f838ae88e4a5a8e54f37099f and fixed in 6.18.40 with commit 5492799ec5d27be3bd454dcaf046bc7054f637ae
Issue introduced in 5.8 with commit 8230fd8217b7ea76f838ae88e4a5a8e54f37099f and fixed in 7.1.5 with commit e3e59ff22a0de01ed0cf3a3e25558811abc3b70a
Issue introduced in 5.8 with commit 8230fd8217b7ea76f838ae88e4a5a8e54f37099f and fixed in 7.2-rc2 with commit 794a01110390c1b76f59ece773fb0fbfd89c6f5c
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-72373
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/callback.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/a99a617701186dc68c7b330d35fc2253f48e2ab2
https://git.kernel.org/stable/c/5492799ec5d27be3bd454dcaf046bc7054f637ae
https://git.kernel.org/stable/c/e3e59ff22a0de01ed0cf3a3e25558811abc3b70a
https://git.kernel.org/stable/c/794a01110390c1b76f59ece773fb0fbfd89c6f5c
reply other threads:[~2026-08-15 6:27 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=2026081516-CVE-2026-72373-c10b@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.