From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74433: rxrpc: Fix UAF in rxgk_issue_challenge()
Date: Sat, 15 Aug 2026 15:12:40 +0900 [thread overview]
Message-ID: <2026081515-CVE-2026-74433-cada@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix UAF in rxgk_issue_challenge()
Fix rxgk_issue_challenge() to free the page containing the challenge
content after invoking the tracepoint as the whdr passed to the tracepoint
points into the page just freed.
The Linux kernel CVE team has assigned CVE-2026-74433 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a and fixed in 6.18.40 with commit 844b8525ce503405c462ad67f750bec648720397
Issue introduced in 6.16 with commit 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a and fixed in 7.1.5 with commit 83bb0ed050e2ad9453d8ef50e4d6e624eac6eed8
Issue introduced in 6.16 with commit 9d1d2b59341f58126a69b51f9f5f8ccb9f12e54a and fixed in 7.2-rc1 with commit 107a4cb0d47e735830f852d83970d5c81f8e1e08
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-74433
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:
net/rxrpc/rxgk.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/844b8525ce503405c462ad67f750bec648720397
https://git.kernel.org/stable/c/83bb0ed050e2ad9453d8ef50e4d6e624eac6eed8
https://git.kernel.org/stable/c/107a4cb0d47e735830f852d83970d5c81f8e1e08
reply other threads:[~2026-08-15 6:40 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=2026081515-CVE-2026-74433-cada@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox