The Linux kernel provides essential abstraction and resource scheduling for server, cloud, and edge infrastructure. Vulnerabilities in core subsystems like net/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI) pose severe risks to multi-tenant workloads, container isolation, and bare-metal servers.
Parameter
Technical Specification
Threat Intelligence Context
CVE Identifier
CVE-2026-31633
Linux Kernel Stable Security Advisory
Vulnerable Subsystem
net/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI)
Core Linux Kernel Subsystem
Weakness Class
CWE-190: Integer Overflow or Wraparound
Memory Safety / Boundary Verification Failure
CVSS v3.1 Score
8.1 (HIGH / Hermes Score 88)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Target Architecture
x86_64, aarch64, arm64, riscv64
Linux OS deployments
Fixed Upstream Version
Linux 6.18.23
Distributed across LTS branches (6.6, 6.12, 6.18+)
An examination of the vulnerable code in net/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI) reveals how input sanitization and lifecycle state tracking fail under specific operational conditions.
// Vulnerability in net/rxrpc/rxgk.c (rxgk_verify_response)
When conditions trigger this code path, internal pointer offsets or memory descriptors deviate from allocated boundaries. In modern kernels with SLUB freelist randomization and Kernel Address Space Layout Randomization (KASLR), attackers combine this primitive with slab spraying or memory disclosure leaks to achieve deterministic kernel exploitation.
Initial Vector & Preconditions: An attacker transmits a crafted RxRPC CHALLENGE_RESPONSE packet on UDP port 7001 with token_len set to 0xFFFE.
Triggering Primitive: The attacker provides crafted parameters or invokes specific system calls that exercise the vulnerable path in net/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI).
Memory Corruption: VULNERABILITY: token_len + round_up can overflow u16 when token_len is near 0xFFFF.
Impact Realization: The corruption yields either instant denial of service (kernel panic, taking down mission-critical cloud instances) or elevation of privilege granting root access across container boundaries.
Security operations centers (SOC) and DFIR incident responders must leverage kernel crash analysis, system logs, and eBPF probes to detect exploitation attempts.
Kernel Ring Buffer (dmesg)
Inspect /var/log/dmesg or journalctl -k for crash signatures matching:
kernel BUG at mm/slub.c or general protection fault in rxgk_verify_response / skb_copy_bits. Look for KASAN warnings or unhandled page faults in net/rxrpc/rxgk.c.
Linux Auditd & Syscall Traces
Audit rules tracking process execution, module interaction, or anomalous device access. Correlate with Linux Process Memory Analysis.
Immediate remediation requires updating the Linux kernel to patched upstream releases and implementing defense-in-depth mitigations.
Kernel Upgrade: Apply distribution security updates providing Linux kernel version 6.18.23 or backported patches from your vendor (RHEL, Ubuntu, Debian, SUSE).
Subsystem Isolation: Where the affected subsystem is compiled as a loadable kernel module (.ko), blacklist the module if not strictly required in /etc/modprobe.d/blacklist.conf.
Kernel Hardening: Ensure sysctl -w kernel.kptr_restrict=2 and sysctl -w kernel.dmesg_restrict=1 to prevent unprivileged pointer disclosure.