Error Handling Flaw in Linux Kernel rxrpc

Publication date: 2026-05-27

Last updated on: 2026-06-16

Assigner: 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).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-16

Generated

2026-07-06

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-46010

EUVD

EUVD-2026-32307

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	6.17
linux	linux_kernel	6.17
linux	linux_kernel	From 6.16.9 (inc) to 6.17 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.4 (exc)
linux	linux_kernel	From 6.17.1 (inc) to 6.18.27 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's rxrpc component, specifically in the function rxgk_extract_token(). The issue was a missing piece of error handling: when the function rxgk_decrypt_skb() returns an -ENOMEM error (indicating an out-of-memory condition), rxgk_extract_token() should return that error immediately instead of continuing execution. For other errors, the function generates an abort, but this specific case was not handled correctly.

Impact Analysis

If the error handling in rxgk_extract_token() is incorrect, it could lead to improper processing of tokens when an out-of-memory error occurs. This might cause unexpected behavior or instability in the kernel's rxrpc subsystem, potentially leading to crashes or denial of service conditions.

Hi! I’m here to help you understand CVE-2026-46010. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70