38 points cobychapple 3 hours ago 27 comments
rvz 2 hours ago | parent
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.
worthless-trash 2 hours ago | parent
Edit: also thanks for using RCE correctly, it seems to be any kind of code execution these days is considered "RCE".. boo.
MithrilTuxedo 2 hours ago | parent
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.
Things won't get worse for too long. If we haven't already surpassed it, we're approaching the point of being able to do static analysis and ensure the mathematical correctness of the most complex C programs ever written so far.
I don't use C or C++, but look how much safer it is to use C or C++ these days.
spauldo 2 hours ago | parent
schainks 56 minutes ago | parent
perching_aix 1 hour ago | parent
The state of cope:
- models are still not intelligent, they're just like, uhh, really good semantic fuzzers! so you can just put them in the loop, they'll fuzz your code, and all is good :)
- the number of bugs is "finite", so - esp with agentic help - we'll just catch up and all will be good :)
Annoyingly, the cope frontier is kinda right about both of these, so the joke shall go on. The only real counter to it would be to bring up that this finiteness claim only really applies to a frozen set of security boundaries and attack surfaces, but they'll probably just raise this being "an academic tier concern" and just tell you to ""fuzz"" more.
So ironically, it looks like these practices are rescued once again, and the bare minimum stays winning. It also starts being moved to the territory of the magic box, but I guess nobody cares about that anymore. Local AI will just get really good too, fully competitive and self hostable even. Any day now.
From the horse's mouth, in case you were suspecting these descriptions to be in bad faith: https://www.youtube.com/watch?v=NnV_cWeoo5Q
drdexebtjl 1 hour ago | parent
Are they? Distributions are rating this at a lower severity presumably because it can’t be easily exploited.
majorchord 2 hours ago | parent
Not sure why the article doesn't mention it, but you can specifically check for MPTCP listeners using `ss -M`.
drum55 2 hours ago | parent
> ListenConfig now uses MPTCP by default on systems where it is supported (currently on Linux only).
This seems to imply basically any golang server built since February 2025 is going to be at least attempting to use it.
aarjaneiro 38 minutes ago | parent
Luckily though, ListenConfig lets you override this https://cs.opensource.google/go/go/+/refs/tags/go1.27.3:src/...
raggi 1 hour ago | parent
superkuh 2 hours ago | parent
ReDress 2 hours ago | parent
Article describes the technical aspects of the bug, how it got handled by different vendors...AI position on it...
But, one would always ask themselves, why did the author write this article? That part hasn't been clear to me even after going through much of the article.
vikramkr 57 minutes ago | parent
drum55 2 hours ago | parent
gnabgib 1 hour ago | parent
Ubuntu (34 points, 16 hours ago, 3 comments) https://news.ycombinator.com/item?id=50287647
CVE.org (2 points, 7 hours ago) https://news.ycombinator.com/item?id=50295879
GoogleGroups (slight tangent) Go programs enable MPTCP by default, exposing them to Linux CVE-2026-98432 (9 points, 3 hours ago, 4 comments) https://news.ycombinator.com/item?id=50298526
walrus01 38 minutes ago | parent
aussieguy1234 1 hour ago | parent
cadamsdotcom 1 hour ago | parent
Everyone using LLMs needs to stop shipping their first draft.
walrus01 40 minutes ago | parent
walrus01 50 minutes ago | parent
It doesn't appear until you've read the page for maybe 10-15 seconds, so if you're not seeing it, just wait.
It even managed to get past ublock origin, since there's no specific rule for it yet.
snvzz 39 minutes ago | parent
None of this can ever affect seL4[0] nor a system built on it, due to its architecture.