Skip to main content

Linux Kernel CVE-2026-31637

| EUVDEUVD-2026-25530 CRITICAL
2026-04-24 Linux GHSA-45qq-4p94-jp2v
Critical
Disputed · 9.8 NVD
Share

Severity by source

Sources disagree (Medium–Critical)
NVD PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SUSE
CRITICAL
qualitative
Red Hat
5.5 MEDIUM
qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

8
Re-analysis Queued
Apr 27, 2026 - 20:22 vuln.today
cvss_changed
Patch released
Apr 27, 2026 - 20:20 nvd
Patch available
Analysis Generated
Apr 27, 2026 - 15:39 vuln.today
CVSS changed
Apr 27, 2026 - 15:22 NVD
9.8 (CRITICAL)
Patch available
Apr 24, 2026 - 16:16 EUVD
EUVD ID Assigned
Apr 24, 2026 - 15:00 euvd
EUVD-2026-25530
Analysis Generated
Apr 24, 2026 - 15:00 vuln.today
CVE Published
Apr 24, 2026 - 14:44 nvd
CRITICAL 9.8

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

rxrpc: reject undecryptable rxkad response tickets

rxkad_decrypt_ticket() decrypts the RXKAD response ticket and then parses the buffer as plaintext without checking whether crypto_skcipher_decrypt() succeeded.

A malformed RESPONSE can therefore use a non-block-aligned ticket length, make the decrypt operation fail, and still drive the ticket parser with attacker-controlled bytes.

Check the decrypt result and abort the connection with RXKADBADTICKET when ticket decryption fails.

AnalysisAI

Unauthenticated remote attackers can exploit a cryptographic validation bypass in the Linux kernel's RxRPC rxkad authentication handler to potentially execute arbitrary code or cause denial of service. The rxkad_decrypt_ticket() function fails to verify that RXKAD response ticket decryption succeeded before parsing the buffer contents, allowing malformed RESPONSE packets with non-block-aligned ticket lengths to drive the ticket parser with attacker-controlled ciphertext bytes. Despite the critical 9.8 CVSS score indicating network-exploitable attack with high impact across confidentiality, integrity, and availability, EPSS exploitation probability is low (0.02%, 5th percentile) and no active exploitation or public POC has been identified. Patches are available across multiple stable kernel versions (6.6.135, 6.12.82, 6.18.23, 6.19.13, 7.0).

Technical ContextAI

This vulnerability exists in the Linux kernel's RxRPC implementation, specifically in the rxkad (RX Kerberos-style Authentication and Data security) protocol handler used for securing AFS (Andrew File System) communications. The rxkad_decrypt_ticket() function uses the kernel's crypto_skcipher_decrypt() API to decrypt authentication response tickets but proceeds to parse the decryption buffer without checking the return code. In cryptographic implementations, failed decryption operations leave the buffer in an undefined state (typically containing unmodified ciphertext or garbage). By crafting a RESPONSE packet with a ticket length that is not aligned to the cipher's block size, an attacker can force decryption to fail while still controlling the bytes that the subsequent parser interprets as a 'decrypted' ticket structure. This violates the fundamental security principle that encrypted data integrity must be validated before use. The vulnerability has existed since commit 17926a79320afa9b (kernel 2.6.22 era) and affects all CPE-identified Linux kernel versions until the patches were applied. The fix adds explicit error checking and returns RXKADBADTICKET (bad ticket error code) to abort the connection when decryption fails.

RemediationAI

Upgrade to patched Linux kernel versions: 6.6.135 or later for 6.6.x series, 6.12.82+ for 6.12.x, 6.18.23+ for 6.18.x, 6.19.13+ for 6.19.x, or 7.0+ for mainline. Patches are available from kernel.org stable repository with commit hashes fe4447cd95623b1cfacc15f280aab73a6d7340b2, 58fcd1b156152613ba00a064a129fb69507ddd7d, 22f6258e7b31dba9bf88dce4e3ee7f0f20072e60, a149dcae23309df9de1c3b6b5d468610ef5ab7de, and 47073aab8a3a5a7b41c9bd37d2a3dcbeeccd6c8a depending on kernel branch. If immediate patching is not feasible, disable RxRPC protocol support by preventing rxrpc kernel module loading (add 'install rxrpc /bin/true' to /etc/modprobe.d/disable-rxrpc.conf and reboot, or use 'rmmod rxrpc' if currently loaded with no active connections). This mitigation completely eliminates the attack surface but will break AFS client functionality and any applications dependent on RxRPC. Systems not using AFS or RxRPC can safely apply this workaround indefinitely. Verify mitigation effectiveness by confirming 'lsmod | grep rxrpc' returns no results and netstat shows no RXRPC sockets listening.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

CVE-2026-31637 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy