CVE-2026-31696: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-05-01 · updated 2026-10-15
Weakness: CWE-787

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing validation of ticket length in non-XDR key preparsing In rxrpc_preparse(), there are two paths for parsing key payloads: the XDR path (for large payloads) and the non-XDR path (for payloads <= 28 bytes). While the XDR path (rxrpc_preparse_xdr_rxkad()) correctly validates the ticket length against AFSTOKEN_RK_TIX_MAX, the non-XDR path fails to do so. This allows an unprivileged user to provide a very large ticket length. When this key is later read via rxrpc_read(), the total token size (toksize) calculation results in a value that exceeds AFSTOKEN_LENGTH_MAX, triggering a WARN_ON(). [ 2001.302904] WARNING: CPU: 2 PID: 2108 at net/rxrpc/key.c:778 rxrpc_read+0x109/0x5c0 [rxrpc] Fix this by adding a check in the non-XDR parsing path of rxrpc_preparse() to ensure the ticket length does not exceed AFSTOKEN_RK_TIX_MAX, bringing it into parity with the XDR parsing logic.

Affected products

Linux kernel: from 3.17 before 6.6.136; from 6.7 before 6.12.84; from 6.13 before 6.18.25; from 6.19 before 7.0.2; 7.1-rc1, 7.1-rc2 — fixed in 6.12.84, 6.18.25, 6.6.136, 7.0.2

How to fix

Upgrade to a fixed version: Linux kernel 6.12.84, 6.18.25, 6.6.136, 7.0.2. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-31696 or the next vulnerability affects your stack