CVE-2026-99725 in Linuxinfo

Summary

by MITRE • 11/20/2026

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

cipso: fix optlen corruption in cipso_v4_delopt()

cipso_v4_delopt() recomputes the option length by walking the option buffer after the CIPSO option has been moved out. The walk then reads the stale bytes at the tail of the buffer as option data, and a crafted setsockopt(IP_OPTIONS) buffer can make it treat one of them as an option length, increasing opt->opt.optlen beyond the valid option data.

The corrupted length stays on the socket and is later used as the copy length by getsockopt(IP_OPTIONS) and by the udp/raw/ping sendmsg paths, where it exceeds the size of the buffers they copy into.

Compute the new length from the intact options before the move and subtract the CIPSO length, and fill the padding with IPOPT_END.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in the Linux kernel involves a critical memory corruption flaw within the Common Infrastructure Policy Specification for IPv4 implementation, specifically affecting the cipso_v4_delopt function. This routine is responsible for removing specific network options from socket buffers during packet processing or configuration changes. The core technical defect lies in how the function recalculates the total length of remaining IP options after a CIPSO option has been removed. Instead of accurately determining the new boundary of valid data, the implementation walks through the buffer and reads stale bytes located at the tail end of the original allocation as if they were legitimate option headers. This logic error allows an attacker who can craft specific setsockopt calls with IP_OPTIONS to manipulate the internal state of the socket by causing it to interpret uninitialized or garbage memory content as a valid option length field.

This misinterpretation leads directly to heap-based buffer overflow conditions because the corrupted optlen value exceeds the actual size of the remaining valid option data. Once this inflated length is stored in the socket structure, it persists and propagates through subsequent network operations. Specifically, when getsockopt is invoked with IP_OPTIONS, or during sendmsg operations for UDP, raw sockets, or ping protocols, the kernel uses this corrupted length to determine how much data to copy into user-space buffers or transmit over the network. Since the reported length exceeds the actual buffer capacity, standard memory copying functions may write beyond allocated boundaries, resulting in out-of-bounds writes that can corrupt adjacent heap structures or cause kernel panics due to invalid memory access patterns.

From a threat modeling perspective, this flaw aligns with CWE-120 Buffer Copy without Checking Size of Input and CWE-787 Out-of-Bounds Write, as the root cause is an unchecked computation leading to buffer overruns. In terms of attack vectors, it falls under ATT&CK technique T1546 Event Triggered Execution if leveraged for privilege escalation via kernel exploitation, or potentially T1059 Command and Scripting Interpreter if used in conjunction with other vulnerabilities to execute arbitrary code. The vulnerability requires local access to modify socket options, making it a potential path for local privilege escalation from an unprivileged user context to root level within the operating system environment.

The remediation strategy implemented addresses this by changing the calculation logic to derive the new option length based on intact options prior to any modification rather than relying on post-move buffer inspection. By subtracting the CIPSO length from the original valid total and ensuring padding is correctly filled with IPOPT_END markers, the kernel maintains accurate bounds for all subsequent operations. This fix ensures that optlen never exceeds the actual amount of valid option data present in the buffer. System administrators should apply the latest available kernel updates to mitigate this risk, as unpatched systems remain vulnerable to crafted socket option requests that can trigger memory corruption and potentially lead to remote code execution or denial of service conditions depending on how the corrupted heap state is exploited by subsequent system calls.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00168

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!