LiquidFiles Documentation
LiquidFiles Documentation

CVE-2026-99288 — Linux kernel TCP socket reuse race

On the 11th of November, 2026, CVE-2026-99288 was published. It is a use-after-free / stale-object race in the Linux kernel's TCP established-connection lookup path (IPv4 and IPv6). Ubuntu has assigned it a Medium priority.

TCP established-socket lookups (__inet_lookup_established() and __inet6_lookup_established()) are lockless and rely on SLAB_TYPESAFE_BY_RCU slabs, so the underlying memory can be reused for a new socket before a concurrent reader has finished with it. After matching a connection tuple, the lookup takes a reference and re-checks the tuple, but it does not check whether the object it just referenced is still hashed. If the same memory is reused — for example when a SYN cookie request socket replaces an earlier one with the same tuple — the lookup can return a reference to the new, unhashed object. A NULL listener pointer on that object then leads to a NULL pointer dereference and kernel panic. See the Ubuntu security tracker for more information.

Impact to LiquidFiles

Does this impact LiquidFiles — Yes, at the operating system level.

The vulnerability is in the Linux kernel shipped with Ubuntu 22.04 LTS, which LiquidFiles is built on. It is not in the LiquidFiles application code. The attack vector is the network, with no privileges or user interaction required, and the impact is a kernel panic (denial of service) rather than data exposure or code execution.

This is a kernel issue, so no LiquidFiles application update can fix it. Ubuntu currently lists the fix for 22.04 LTS (jammy) as needing evaluation.

When will this be fixed

This will be fixed when Ubuntu releases an updated kernel for Ubuntu 22.04 LTS. You can check the current patch status on the Ubuntu security tracker.

When the kernel update is released and you have Automatic Updates enabled as recommended, the updated kernel package will be installed automatically. A reboot is needed to start using the new kernel.