News for hackers. Stuff that matters.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by praseodym on Wednesday November 18, 2026 @12:11PM (#50548942)
The blog post is very difficult to read, I suspect that unfortunately it’s fully written by an LLM.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by Betelbuddy on Wednesday November 18, 2026 @12:20PM (#50549095)
The LLMs find the security issues, the LLMs will write the reports and the LLMs will fix and patch them.

I guess its time for all of us to step aside, leave space for somebody who knowns what they are doing, and go fishing...

Re:CVE-2026-99312: KVM Guest-to-Host Escape by praseodym on Wednesday November 18, 2026 @12:25PM (#50549167)
And this way only LLMs can learn from these vulnerabilities, making it even more likely that the next one will be found by an LLM.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by catlifeonmars on Wednesday November 18, 2026 @01:16PM (#50549922)
[delayed]
Re:CVE-2026-99312: KVM Guest-to-Host Escape by cduzz on Wednesday November 18, 2026 @01:47PM (#50550379)
We're all living in the story of mel.

At first, there were just big logic blocks and storage that did as they were told.

Later, in hardware, there were all sorts of optimizations built in where the logic would do its own thing -- so you'd get caches and speculative execution and even on-the-fly conversion from one instruction set to another.

This abstraction was also piled onto the runtime -- you'd write machine code, then assembly, then higher level languages; eventually you'd run in interpreted or just-in-time generated bytecode (hello to Java from UCSD p-System from the 70s and Burroughs machines in the 60s). And of course... operating systems...

Now, we've got machines reading source code (and machine code, and everything in between) and they've got some ability to thing the thing to make it thing. Sometimes correctly (enough to pass existing tests) and sometimes without the ability to express to the human what the thing they thinged was.

But, we're all living in the land of mel and for some it's always been better to go fishing than to pretend to participate.

Re:CVE-2026-99312: KVM Guest-to-Host Escape by immibis2 on Wednesday November 18, 2026 @04:33PM (#50552416)
The "hardware doing its own thing" can be understood. There was this big ideological movement called ECS in the 2010s that was about writing software in ways that actually run well on hardware.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by xlayn on Wednesday November 18, 2026 @12:40PM (#50549422)
doesn't change the value of what's writen, if true and actionable that's all that should be needed
Re:CVE-2026-99312: KVM Guest-to-Host Escape by drum55 on Wednesday November 18, 2026 @12:47PM (#50549519)
If it was valuable a human would have been able to communicate it in a few lines of text. Using a LLM to blast slop devalues everything and communicates little. A drunken twitter rant has more ability to convey information than sloppy blog posts with 3 pieces of information per sentence.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by cluckindan on Wednesday November 18, 2026 @12:54PM (#50549634)
Just ask the clanker to read it buddy, you’re already behind /s
Re:CVE-2026-99312: KVM Guest-to-Host Escape by bigfishrunning on Wednesday November 18, 2026 @12:57PM (#50549667)
It's inverse compression!
Re:CVE-2026-99312: KVM Guest-to-Host Escape by Ylpertnodi on Wednesday November 18, 2026 @01:23PM (#50550019)
Get hip to it, daddy-o.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by Pannoniae on Wednesday November 18, 2026 @02:46PM (#50551138)
these squares aint hip to the jive, I know that!
Re:CVE-2026-99312: KVM Guest-to-Host Escape by sylos on Wednesday November 18, 2026 @01:06PM (#50549783)
Value is more than just iron something is made from. How it's shaped and presented is just as important
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tptacek on Wednesday November 18, 2026 @01:21PM (#50549995)
No, it is not "just as important" as the underlying information.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by tsunagatta on Wednesday November 18, 2026 @01:36PM (#50550217)
It actually might be far more important. You are a lot more important than the molecules that you are made of
Re:CVE-2026-99312: KVM Guest-to-Host Escape by mahogany on Wednesday November 18, 2026 @01:59PM (#50550529)
[delayed]
Re:CVE-2026-99312: KVM Guest-to-Host Escape by catlifeonmars on Wednesday November 18, 2026 @01:15PM (#50549904)
[delayed]
Re:CVE-2026-99312: KVM Guest-to-Host Escape by Kozmik1 on Wednesday November 18, 2026 @03:37PM (#50551801)
OP (me) was not the author but I generally agree - a well written or at least better edited summary as a preamble would have been preferable, however it's educational to see the process and a potential repro of the issue don't you think?

Of course I imagine they used AI to find the exploit, and the documentation may have come as an output from that process.

Re:CVE-2026-99312: KVM Guest-to-Host Escape by manbash on Wednesday November 18, 2026 @01:17PM (#50549941)
It has "potential", not "value".

Also in this case, a "missed potential" if it eventually fails to reach anyone.

Re:CVE-2026-99312: KVM Guest-to-Host Escape by InsidiousWombat on Wednesday November 18, 2026 @01:26PM (#50550066)
well it's 404 now
Re:CVE-2026-99312: KVM Guest-to-Host Escape by orbital-decay on Wednesday November 18, 2026 @05:47PM (#50553453)
Like someone have said very long ago, "If."
Re:CVE-2026-99312: KVM Guest-to-Host Escape by biotechbio on Wednesday November 18, 2026 @12:42PM (#50549445)
Glad to see this is the top comment. This is written by Claude, I know because I talk to Claude for 8+ hours a day, and it says stuff like this. I stopped reading the article because of it.
Re:CVE-2026-99312: KVM Guest-to-Host Escape by JeremyNT on Wednesday November 18, 2026 @01:44PM (#50550342)
And now it seems to have been pulled (getting a 404).

Perhaps they are rewriting it with less slop?