Skip to content

CVE-2026-31633: Linux Kernel AF_RXRPC rxgk Token Handling Integer Overflow

HERMES

HERMES THREAT SCORE & LINUX KERNEL ATTACK SURFACE

Target: net/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI)
Confidence: 95%
88 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 18 / 20
Threat Activity 16 / 20
Weaponization 17 / 20
Exposure 18 / 20
Prevalence 19 / 20
Impact 18 / 20
Exploit Maturity 17 / 20
Attack Chain Potential 19 / 20
⚖️ Divergence & Operational Rationale

CVSS v3.1 rates CVE-2026-31633 at 8.1 (HIGH, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). The Hermes Threat Score evaluates operational impact at 88 (HIGH) considering kernel-level exploitation potential and critical subsystem placement.

🕸️ Connected Knowledge Graph & Provenance

CVE-2026-31633: Linux Kernel AF_RXRPC rxgk Token Handling Integer OverflowVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTLinux Kernel Core
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

🔍 Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Linux Kernel Core documented in Hermes dossier.”

Supporting Verified Evidence:

1. Technical Context & Affected Subsystems

Section titled “1. Technical Context & Affected Subsystems”

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.

ParameterTechnical SpecificationThreat Intelligence Context
CVE IdentifierCVE-2026-31633Linux Kernel Stable Security Advisory
Vulnerable Subsystemnet/rxrpc/rxgk.c (AF_RXRPC / AFS Kerberos GSSAPI)Core Linux Kernel Subsystem
Weakness ClassCWE-190: Integer Overflow or WraparoundMemory Safety / Boundary Verification Failure
CVSS v3.1 Score8.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 Architecturex86_64, aarch64, arm64, riscv64Linux OS deployments
Fixed Upstream VersionLinux 6.18.23Distributed across LTS branches (6.6, 6.12, 6.18+)
MITRE ATT&CKT1190 - Exploit Public-Facing Application, T1040 - Network SniffingKernel Exploitation and Defense Evasion
Forensic Cross-ReferenceLinux Process Memory AnalysisMemory analysis and system artifact tracing

2. In-Depth Technical Decomposition & Root Cause

Section titled “2. In-Depth Technical Decomposition & Root Cause”

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)
int rxgk_verify_response(struct rxrpc_connection *conn, struct sk_buff *skb)
{
struct rxgk_response resp;
u16 token_len;
size_t alloc_len;
if (skb_copy_bits(skb, 0, &resp, sizeof(resp)) < 0)
return -EPROTO;
token_len = ntohs(resp.token_len);
/* VULNERABILITY: token_len + round_up can overflow u16 when token_len is near 0xFFFF */
alloc_len = round_up(token_len + sizeof(struct rxgk_header), 8);
/* alloc_len wraps around, allocating a undersized heap chunk */
conn->rxgk.buffer = kzalloc(alloc_len, GFP_NOFS);
if (!conn->rxgk.buffer)
return -ENOMEM;
/* skb_copy_bits uses un-truncated token_len, overflowing heap */
return skb_copy_bits(skb, sizeof(resp), conn->rxgk.buffer, token_len);
}

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.


  1. Initial Vector & Preconditions: An attacker transmits a crafted RxRPC CHALLENGE_RESPONSE packet on UDP port 7001 with token_len set to 0xFFFE.
  2. 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).
  3. Memory Corruption: VULNERABILITY: token_len + round_up can overflow u16 when token_len is near 0xFFFF.
  4. 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.

4. Forensic Detection, Artifacts & System Logs

Section titled “4. Forensic Detection, Artifacts & System Logs”

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.

sigma_kernel_cve_2026_31633.yaml
title: Linux Kernel RxRPC Anomalous Token Memory Allocation
id: cve-2026-31633
status: experimental
description: Detects kernel error signatures and abnormal syscall behaviors associated with CVE-2026-31633.
logsource:
category: kernel
product: linux
detection:
selection_dmesg:
- 'kernel'
- 'net'
condition: selection_dmesg
fields:
- Message
- Hostname
falsepositives:
- Hardware memory faults or unpatched test suites
level: high

Immediate remediation requires updating the Linux kernel to patched upstream releases and implementing defense-in-depth mitigations.

  1. Kernel Upgrade: Apply distribution security updates providing Linux kernel version 6.18.23 or backported patches from your vendor (RHEL, Ubuntu, Debian, SUSE).
  2. 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.
  3. Kernel Hardening: Ensure sysctl -w kernel.kptr_restrict=2 and sysctl -w kernel.dmesg_restrict=1 to prevent unprivileged pointer disclosure.
  4. Runtime Integrity: For comprehensive persistent threat hunting, consult our guide on Linux Process Memory Analysis.