Menu

Star on GitHub · 3.2k

CVE-2026-31696

7.8 · HIGH

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 k…

Published May 1, 2026CWE-787EPSS 0.18%

Overview

CVE-2026-31696 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31696?

CVE-2026-31696 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31696?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31696?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31696?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31696 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all