Hacker News
NoisyTCP
george_max
|next
[-]
goodmythical
|root
|parent
[-]
It seems to rely on micro-second timing that isn't really available over generic public infra. Perhaps if chained with other techniques that allow the attacker to launch this from within someone's private infra, but then we're in the "if they're in they're in" realm.
There are published mitigations (disable syncookies, serialize queue) as well, so the number will shrink as systems are patched.
eta: also fixed in available kernels https://security-tracker.debian.org/tracker/CVE-2026-99288
Bender
|previous
[-]
NoisyTCP / CVE-2026-99288 fixed in 6.18.63 [1][2][3][4][5]
[1] - https://nvd.nist.gov/vuln/detail/CVE-2026-99288
[2] - https://github.com/V4bel/NoisyTCP
[3] - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux...
[4] - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
[5] - https://www.cyberkendra.com/2026/11/cve-2026-99288-noisytcp-...