From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46010: rxrpc: Fix error handling in rxgk_extract_token()
Date: Wed, 27 May 2026 14:59:01 +0200 [thread overview]
Message-ID: <2026052744-CVE-2026-46010-e0b6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix error handling in rxgk_extract_token()
Fix a missing bit of error handling in rxgk_extract_token(): in the event
that rxgk_decrypt_skb() returns -ENOMEM, it should just return that rather
than continuing on (for anything else, it generates an abort).
The Linux kernel CVE team has assigned CVE-2026-46010 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.17 with commit 64863f4ca4945bdb62ce2b30823f39ea9fe95415 and fixed in 6.18.27 with commit 293095ef618818852bac5488c1bc223935e2ca17
Issue introduced in 6.17 with commit 64863f4ca4945bdb62ce2b30823f39ea9fe95415 and fixed in 7.0.4 with commit c52803e925604e2a17962ab0c99dce2d3f7238db
Issue introduced in 6.17 with commit 64863f4ca4945bdb62ce2b30823f39ea9fe95415 and fixed in 7.1-rc1 with commit 3476c8bb960f48e49355d6f93fb7673211e0163f
Issue introduced in 6.16.9 with commit 8ac99c57029e13ebb5fb0d634925abedef32b53a
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-46010
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_app.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/293095ef618818852bac5488c1bc223935e2ca17
https://git.kernel.org/stable/c/c52803e925604e2a17962ab0c99dce2d3f7238db
https://git.kernel.org/stable/c/3476c8bb960f48e49355d6f93fb7673211e0163f
reply other threads:[~2026-05-27 13:02 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=2026052744-CVE-2026-46010-e0b6@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.