From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80885: afs: Fix uncancelled rxrpc OOB message handler
Date: Fri, 4 Sep 2026 18:46:52 +0200 [thread overview]
Message-ID: <2026090438-CVE-2026-80885-7716@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix uncancelled rxrpc OOB message handler
Fix AFS to cancel its OOB message processing (typically to respond to
security challenges). Also move OOB message processing to afs_wq so that
it's also waited for and make the OOB handler just return if the net
namespace is no longer live.
The Linux kernel CVE team has assigned CVE-2026-80885 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 5800b1cf3fd8ccab752a101865be1e76dac33142 and fixed in 6.18.40 with commit 231414253b648b3518b56f09710b831945d6a2fc
Issue introduced in 6.16 with commit 5800b1cf3fd8ccab752a101865be1e76dac33142 and fixed in 7.1.5 with commit d14e96ddd616c8a9fff3b5bab3bf4af0cfc30ec4
Issue introduced in 6.16 with commit 5800b1cf3fd8ccab752a101865be1e76dac33142 and fixed in 7.2 with commit a4057e58b07005d0fe0491bdbf1868c1491909ee
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-80885
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/cm_security.c
fs/afs/rxrpc.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/231414253b648b3518b56f09710b831945d6a2fc
https://git.kernel.org/stable/c/d14e96ddd616c8a9fff3b5bab3bf4af0cfc30ec4
https://git.kernel.org/stable/c/a4057e58b07005d0fe0491bdbf1868c1491909ee
reply other threads:[~2026-09-04 16:53 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=2026090438-CVE-2026-80885-7716@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.