CVE-2026-98432：Linux TCP Use-After-Free 風險與修補驗證

Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

CVE-2026-98432: Linux TCP Use-After-Free Risk and Patch Validation (penligent.ai) 10 points by cobychapple1 hour ago | hide | past | favorite | 6 comments help majorchord11 minutes ago | next[–] Thankfully the vast majority of servers are not creating MPTCP listeners by default (that I'm aware of). Not sure why the article doesn't mention it, but you can specifically check for MPTCP listeners using ss -M. reply superkuh8 minutes ago | prev | next[–] Would dropping these specialized ipv4 syn packets with extra header size beyond 20 bytes with the firewall (iptables/nftables/etc) be low enough in the order of things to mitigate the attack? Like, iptables -A INPUT -p tcp --syn -m u32 --u32 "0>>24&0xF=6:15" -j DROP ? reply rvz21 minutes ago | prev[–] This one is quite serious and the type of vulnerability is once again, a C style memory corruption and a race condition combined; leading to an RCE. At this point, we seriously need to discuss whether if the major projects still written in C such as Linux, Chromium and even git can even handle the stream of now near infinite bugs being discovered with AI. Attackers are already rapidly finding and building exploits for those vulnerabilities the moment they are discovered with abliterated frontier-level models. These sort of vulnerabilities are far to common in those projects and in the future, it will be extremely unsafe for even experts to continue using C or C++ in any way. reply spauldo2 minutes ago | parent | next[–] Unless someone vibecodes a new OS and convinces everyone to use it, we're stuck with what we got. Reaching feature parity with Linux and then debugging it to the point where it'd be usable is a gargantuan undertaking. reply MithrilTuxedo2 minutes ago | parent | prev | next[–] I bet there's a half-life to bugs though. Bugs might be infinite over the lifespan of a project, but the rate that they are produced goes down with our ability to detect them. A lot are being found now in projects written in C because the backlog of bugs to find is mostly written in C. We haven't yet gotten to the point when we're detecting most bugs before they're released, but we will. reply worthless-trash4 minutes ago | parent | prev[–] Leading 'maybe' to an RCE, i imagine you need to groom the heap first, unless there is something i'm missing. Edit: also thanks for using RCE correctly, it seems to be any kind of code execution these days is considered "RCE".. boo. reply Consider applying for YC's Winter 2027 batch! Applications are open till November 2. Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact Search: