Live › vulnerability › CVE-2026-99270
When a TCP connection migration fails in the kernel's request-socket timer handler, the new request socket can be freed while its timer is still pending. A later timer firing then touches freed memory, which can crash the kernel or be turned into code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 13:20 UTC. All times on this page are UTC.
Any Linux host with a kernel that includes the cited commit can be exposed, since the bug sits in the generic TCP stack. Only hosts where TCP socket migration is in use reach the failing path; the sources do not say how commonly that is enabled by default. Systems that do not run this kernel version can skip it.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel builds from your distributionnet.ipv4.tcp_migrate_req) is enabled: sysctl net.ipv4.tcp_migrate_reqUnknown from the sources.
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:
tcp: Fix potential UAF in reqsk_timer_handler().
When TCP socket migration fails at inet_ehash_insert() in reqsk_timer_handler(), we jump to the no_ownership: label and free the new reqsk immediately with __reqsk_free().
Thus, we must stop the new reqsk's timer before jumping to the label, but the timer might be missed since the cited commit, resulting in UAF.
As we are in the original reqsk's timer context, we can safely call timer_delete_sync() for the new reqsk.
Let's pass false to __inet_csk_reqsk_queue_drop() to stop the new reqsk's timer.
This page as .md · .json · in your agent: get_signal("CVE-2026-99270")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.