Introduction
CVE-2026-99999 is an out-of-bounds write vulnerability in the Linux kernel's IPv4 networking subsystem. A flaw in the skb_checksum_help function allows a local attacker or untrusted guest VM to send packets with malformed checksum metadata, corrupting memory in the network header. Successful exploitation can lead to arbitrary code execution, a denial-of-service crash, or disclosure of sensitive kernel memory.
The vulnerability carries a CVSS v3.1 score of 8.8 (local access, changed scope) and is classified as CWE-787 (Out-of-bounds Write). The upstream fix adds validation of checksum_start before the checksum is completed.
This article covers Rocky Linux 8, 9, and 10 systems, including CIQ LTS, FIPS, and RLC Pro variants. It describes what is affected, the current patch status, and recommended actions.
Problem
The IPv4 networking subsystem in the Linux kernel does not validate the checksum_start offset before completing a checksum operation. A packet with crafted checksum metadata can reach skb_checksum_help, which then writes beyond the bounds of the network header, corrupting adjacent kernel memory. This corruption can be leveraged for code execution, crashing the kernel (DoS), or leaking kernel memory contents.
The following systems should be treated as affected until running a patched kernel listed in the Patched Kernels section:
- Rocky Linux 8, 9, and 10 community releases
- Rocky Linux 8 and 9 LTS variants
- RLC Pro FIPS variants
- RLC Pro variants based on Rocky Linux 8, 9, or 10 including RLC Pro Hardened
The vulnerability requires local code execution or the ability to inject packets from an untrusted guest VM. It is not exploitable by remote unauthenticated attackers sending traffic to a listening service. However, any system with local shell users, shared application accounts, CI runners, KVM guests running untrusted workloads, or containerized workloads that allow packet injection should be treated as exposed.
Status
- Patched kernels are available for all supported variants except LTS 8.8 and FIPS 9.2. See the Patched Kernels table below for specific versions. LTS 8.8 and FIPS 9.2 will be added as builds complete validation.
- No mitigation is currently available. The vulnerable code path is in the core IPv4 networking stack and cannot be disabled via module blocking, sysctl, or firewall rules without breaking network connectivity entirely.
- Recommended action: for variants with available patches, install the patched kernel and reboot. See Installing the Update below for variant-specific instructions. For variants without patches yet, monitor this article for updates.
- For Rocky Linux community releases, refer to Rocky Linux Errata for patched kernel availability and update instructions.
- Open a support case if you need help assessing exposure or tracking patched kernel availability for a specific CIQ variant.
Patched Kernels
| Variant | Patched Kernel Version | Released |
|---|---|---|
| CIQ Bridge 7.9 | kernel-3.10.0-1160.119.1.el7_9.ciqcbr.22.1 |
2026-10-20 |
| RLC Pro LTS 8.6 | kernel-4.18.0-372.32.1+39.1.el8_6_ciq |
2026-10-20 |
| RLC Pro LTS 8.10 | kernel-4.18.0-553.176.1+2.1.el8_10_ciq |
2026-10-22 |
| RLC Pro 8 | kernel-4.18.0-553.176.1+2.1.el8_10_ciq |
2026-10-22 |
| CIQ SIG/Cloud Next 8 | kernel-4.18.0-553.176.1+2.1.el8_10_ciq |
2026-10-22 |
| RLC Pro FIPS 8.6 | kernel-4.18.0-553.176.1+2.1.el8_6.ciqfips |
2026-10-22 |
| RLC Pro FIPS 8.10 | kernel-4.18.0-553.176.1+2.1.el8_10_ciq |
2026-10-22 |
| RLC Pro LTS 9.2 | kernel-5.14.0-284.30.1+44.1.el9_2_ciq |
2026-10-20 |
| RLC Pro LTS 9.6 | kernel-5.14.0-570.60.1+26.1.el9_6_ciq |
2026-10-22 |
| RLC Pro FIPS 9.6 | kernel-5.14.0-570.60.1+26.1.el9_6_ciq |
2026-10-22 |
| RLC Pro 9 | kernel-5.14.0-687.58.1+2.1.el9_8_ciq |
2026-10-22 |
| CIQ SIG/Cloud Next 9 | kernel-5.14.0-687.58.1+2.1.el9_8_ciq |
2026-10-22 |
| RLC Pro 10 | kernel-6.12.0-211.66.1+2.1.el10_2_ciq |
2026-10-22 |
| CIQ SIG/Cloud Next 10 | kernel-6.12.0-211.66.1+2.1.el10_2_ciq |
2026-10-22 |
This table will be updated as CIQ engineering releases validated kernel builds for additional variants.
Confirm what is running on a given system with:
uname -r
If your system reports one of the patched versions above (or newer), the fix is in place.
Installing the Update
RLC Pro LTS and FIPS Variants
For RLC Pro LTS variants (including LTS 8.6, LTS 9.2, LTS 9.6) and FIPS variants, the patched kernel is available directly from the configured CIQ repository. No additional repository configuration is required:
sudo dnf update kernel*
sudo reboot
RLC Pro, LTS 8.10, and SIG/Cloud Next
For RLC Pro 8, RLC Pro 9, RLC Pro 10, LTS 8.10, and CIQ SIG/Cloud Next variants, refresh your DNF metadata and update:
sudo dnf clean all && sudo dnf makecache
sudo dnf update kernel*
sudo reboot
If the update does not appear, confirm that the appropriate depot channel is enabled for your product:
sudo depot enable rlc-pro-9 # RLC Pro 9 / CIQ SIG Cloud Next 9
sudo depot enable rlc-pro-10 # RLC Pro 10 / CIQ SIG Cloud Next 10
CIQ Bridge 7.9
For CIQ Bridge customers, the patched kernel is available from the Bridge repository:
sudo yum update kernel*
sudo reboot
For Rocky Linux community releases, refer to Rocky Linux Errata for patched kernel availability and update instructions.
Notes
Before the patched kernel is available, consider the following risk-limiting measures:
- Attack surface: the vulnerability requires local code execution or the ability to send packets with crafted checksum metadata from within a KVM guest. Systems with no local users, no untrusted guest VMs, and no containerized workloads that allow raw packet construction have a reduced attack surface, though patching remains the recommended action.
- No module-level mitigation: unlike vulnerabilities in optional kernel modules (such as
esp4orrxrpc), the IPv4 checksum path is part of the core networking stack. It cannot be disabled without breaking all IPv4 connectivity. - Exploitation: the vulnerability has been reproduced independently. Treat affected systems with local users or untrusted workloads as exploitable until a patched kernel is installed.