Live › vulnerability › CVE-2026-98625
Go to dashboardIn the Linux netfilter flowtable code, a flow can be marked dead before the offload worker finishes with it, so garbage collection may free it while the worker still uses it. The sources describe this as a use-after-free, which can lead to a crash or memory corruption in the kernel.
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.
Systems running the Linux kernel with netfilter flowtable offload configured, typically routers, firewalls and gateways that use nftables flow offload. Hosts that do not configure flowtables are unlikely to be exposed. The sources do not say which kernel versions are affected.
No product ranges from the sources yet.
uname -r to see the running kernel versionnft list ruleset | grep -i flowtableEach 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:
netfilter: flowtable: publish HW_DEAD after worker is done
flow_offload_work_del() sets NF_FLOW_HW_DEAD before the work handler clears NF_FLOW_HW_PENDING. Once a flow is both HW_DYING and HW_DEAD, a concurrent garbage collection pass can remove it and schedule it for RCU freeing.
The offload worker holds neither an RCU read lock nor a reference to the flow. If it is preempted after publishing HW_DEAD, the RCU callback can free the flow before the worker resumes and clears HW_PENDING, resulting in a use-after-free.
Move HW_DEAD publication to the common worker epilogue after the pending bit is cleared, making it the final flow access by destroy work. Order all preceding flow accesses before publishing the bit that allows garbage collection to free the object.
This page as .md · .json · in your agent: get_signal("CVE-2026-98625")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.