CVE-2026-99494 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

s390/zcrypt: Fix out-of-bounds ptr advance in cca_query_crypto_facility()

The FQ reply parser code blindly advanced the walk pointer by a length value read directly from the hardware reply payload without checking that the advance stayed within the allocated reply buffer. A corrupt or malicious device response could push ptr beyond the cprbmem region, causing an out-of-bounds dereference or kernel memory exposure via the subsequent memcpy().

Fix this by tracking the remaining reply buffer space in a variable and validating each device-supplied length field against it before advancing or dereferencing the pointer.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability identified as CVE-2024-s390-zcrypt involves a critical out-of-bounds memory access flaw within the Linux kernel's s390 zCrypt subsystem, specifically in the cca_query_crypto_facility function. This component is responsible for parsing Facility Query Reply (FQ) messages received from cryptographic hardware devices attached to IBM System z mainframes. The core technical deficiency lies in the parser logic which blindly advances a pointer by a length value extracted directly from the device-supplied payload without performing any bounds checking against the allocated buffer size. In normal operation, this mechanism functions correctly as hardware responses are well-formed and adhere to expected protocols. However, when interacting with compromised, malfunctioning, or maliciously crafted devices that supply oversized or malformed length fields, the pointer arithmetic causes the walk pointer to exceed the boundaries of the cprbmem region. This results in an out-of-bounds dereference where subsequent operations attempt to read from memory locations outside the intended buffer allocation.

The operational impact of this flaw is severe due to its potential for kernel memory exposure and arbitrary code execution. When the pointer advances beyond the allocated reply buffer, the subsequent memcpy operation reads data from adjacent kernel memory structures that were not intended to be accessed by this routine. This can lead to information disclosure where sensitive kernel data such as stack contents, credentials, or other process memories are leaked back through the response mechanism. Furthermore, depending on how the parsed values influence control flow in later stages of processing, an attacker with physical access to a cryptographic card slot could potentially exploit this memory corruption to achieve arbitrary code execution within the kernel space. This represents a significant security risk as it bypasses standard user-space isolation boundaries and compromises the integrity of the entire system hosting the zCrypt hardware.

From a classification perspective, this vulnerability aligns closely with CWE-125 Out-of-bounds Read, which describes reading data outside the bounds of an allocated buffer. It also relates to CWE-787 out-of-bounds write if the subsequent processing leads to memory corruption beyond just read operations. In terms of adversarial tactics, this flaw can be leveraged in attacks categorized under ATT&CK technique T1059 Command and Scripting Interpreter or more specifically T1068 Exploitation for Privilege Escalation when used to gain kernel-level access from a lower-privileged context. The attack vector is primarily physical or local hardware-based, requiring an attacker to have control over the input data sent by the cryptographic device, which limits remote exploitation but increases risk in environments with untrusted peripheral devices or shared infrastructure where malicious actors might insert rogue crypto cards.

Mitigation strategies for this vulnerability involve both immediate patching and long-term architectural improvements. The primary remediation is applying the kernel update that introduces bounds checking logic to track remaining reply buffer space before advancing pointers based on device-supplied length fields. System administrators should ensure their Linux kernels are updated to versions containing this fix, particularly those running on IBM zSeries hardware with attached cryptographic accelerators. Additionally, organizations employing such infrastructure should implement strict physical security controls around crypto card slots and utilize hardware attestation mechanisms where possible to verify the integrity of connected devices before processing sensitive operations. Regular auditing of kernel logs for memory access violations can also help detect attempted exploitation activities in real-time while patches are being deployed across the fleet.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00174

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!