External risk intelligence

Linux kernel allows attackers to read sensitive memory via network access

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-31636

An external attacker can exploit a vulnerability in the Linux kernel to access sensitive system memory. This can lead to the unauthorized exposure of confidential data and may help an attacker bypass security protections to compromise the affected system.

2Halo Surface Signal

Out-of-bounds Read

Linux Kernel

6.16.1 to before 6.18.236.19 to before 6.19.136.167.0

External exposure likelihood

Halo Surface Signal score for CVE-2026-31636

The vulnerability resides in the rxrpc network protocol implementation, primarily used by AFS (Andrew File System). This protocol is typically deployed within internal or restricted enterprise network environments rather than as a public-facing internet service. While network-reachable where the protocol is active, it is not a common candidate for direct public internet exposure.

Horizon Alert

Summary of the vulnerability and why it matters

A flaw in the Linux kernel's RXRPC protocol allows for an out-of-bounds read when processing a malformed response. This could potentially lead to system instability or information disclosure, making it important to address.

  • Affects network protocol processing.
  • Could cause system crashes or data leaks.
  • Requires a specific network service to be running.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this flaw to cause a denial-of-service condition by sending specially crafted network packets to a vulnerable Linux kernel. The rxrpc network protocol is the target, and a successful exploit would lead to an out-of-bounds read, crashing the kernel.

  • Network access required.
  • Malformed RESPONSE authenticator.
  • Exploits rxrpc protocol logic.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability, an out-of-bounds read in the Linux kernel's rxrpc protocol, presents a moderate threat. Attackers are less likely to weaponize this for widespread internet attacks due to the niche nature of the rxrpc protocol, which is not commonly exposed publicly. However, it could be exploited in targeted attacks within environments where AFS is deployed.

  • Exploitation requires specific network conditions.
  • Unlikely for widespread public attacks.
  • Niche protocol limits broad appeal.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize patching or updating Linux kernel versions to mitigate the critical OOB read vulnerability in the rxrpc authenticator parser. If immediate patching is not feasible, focus on network-level controls and monitoring for suspicious rxrpc traffic patterns.

  • Apply kernel patches for affected versions.
  • Implement network ingress filtering for rxrpc.
  • Monitor rxrpc for malformed authenticator requests.

Frequently asked questions

What is the Linux kernel's rxrpc protocol?

The Linux kernel's rxrpc protocol is a network communication mechanism, primarily used by systems like the Andrew File System (AFS). It facilitates data transfer and connection management between different systems over a network.

What kind of weakness does CVE-2026-31636 describe for the Linux kernel?

CVE-2026-31636 describes an out-of-bounds read vulnerability in the Linux kernel's rxrpc protocol. This occurs when the protocol incorrectly parses a malformed RESPONSE authenticator, allowing it to read beyond allocated memory. This is classified as CWE-125.

How could an attacker trigger the Linux kernel vulnerability CVE-2026-31636?

An attacker could trigger this vulnerability by sending specially crafted network packets containing a malformed RESPONSE authenticator to a system running a vulnerable version of the Linux kernel with the rxrpc protocol enabled. The bug is not triggered by malformed network packets that do not conform to the rxrpc protocol's authenticator structure.

Who should care about CVE-2026-31636 in the Linux kernel?

Organizations running Linux kernel versions affected by this vulnerability should care, especially if they utilize the rxrpc protocol, often associated with AFS. While the Halo Surface Signal indicates this is unlikely to be a widespread internet-facing threat, it could be relevant if rxrpc is used internally within a network.

What is the first step to address CVE-2026-31636 in the Linux kernel?

The primary response is to update the Linux kernel to a patched version that resolves the out-of-bounds read issue in the rxrpc protocol. Applying these kernel updates is the most effective way to mitigate the vulnerability.

References