Live › vulnerability › CVE-2026-99064
Go to dashboardWhen the Linux kernel removes a CIPSO option from a packet, it does not adjust cached offsets for IP options that follow it, so later code reads the wrong bytes. The sources do not say what an attacker gets beyond corrupted option handling, though the description notes that option copying may treat packet data as a length and write it into fixed-size storage.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
cipso: adjust cached option offsets when removing CIPSO
cipso_v4_skbuff_delattr() removes the CIPSO bytes but does not adjust cached offsets for options that follow them.
For example, with a valid 10-byte CIPSO option followed by a seven-byte RR option, parsing records rr at offset 30. Removing CIPSO moves RR to offset 20, while the cached offset remains 30. Consumers such as ip_forward_options() and __ip_options_echo() then access the wrong bytes; the latter may interpret packet data as the option length and copy it into fixed-size option storage.
Mirror cipso_v4_delopt() and subtract cipso_len from the srr, rr, ts and router_alert offsets when they follow CIPSO. cipso_len is the distance the first memmove() shifts those options. The later header move and network-header reset relocate the bytes and their offset base together.
This page as .md · .json · in your agent: get_signal("CVE-2026-99064")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.