Linux kernel

Why does it do that?

It usually means the Linux kernel has placed a lock on the virtual optical drive, or maybe it just failed to automatically mount the previous state.

So how do you fix it?

You have to actually power down the VM, go into the hypervisor's hardware settings at the top menu, manually disconnect the virtual CD and DVD drive, and if it's already connected, you disconnect it and reconnect it just to force a state refresh and then boot back up.

Exactly.

The guest additions require kernel-level access, so they can intercept display protocols and modify the clipboard daemon.

By forcing you to use sudo, the Linux kernel is demanding explicit cryptographic authorization from you, the system administrator.

It's basically making you say, I understand that this script is going to alter the core communication layer of this operating system, and I am officially authorizing it.

If England's rugby strategy is to preemptively reward potential failure, maybe they should hire fortune tellers as assistant coaches to guide them through next season's crystal ball predictions.

Linux kernel launch on new platform promises seamless integration.

If the Linux kernel gets any more universal, it'll soon be running on your toaster, calculating the optimal crispness level while pondering the mysteries of the universe with a side of perfectly brown toast.

Trump's DOJ declares training is an infringement amidst fair use battles.

When training in AI is like teaching a parrot to swear, it's all fun and games until lawsuits start squawking.

a benchmark of about 900 instances derived from real-world vulnerabilities in users-based programs.

So there's some JavaScript here, Linux kernel for people who are interested in such things, all intended to measure whether AI agents can convert known vulnerabilities into working exploits.

Sure.

OpenAI was running an internal evaluation based on this benchmark when the incident occurred.

So my name is Seth and I work as a minion on Project Zero.

Most of my time I spend, I've been spending a lot of time looking at Linux kernel.

That's sort of what my background is, is looking for Linux kernel vulnerabilities.

Recently in the past, I've been on the team now for, let's see, it must have been since 2022.

So about four years now.

And then it's the drivers? Yeah.

And then what did you have to do after that? Yeah.

So once you exploit the driver, I mean, so the driver is running in the context of the Linux kernel, right? So if you are finding bugs in the driver, memory corruption bugs, it's the same sort of like memory corruption sort of issues that you could have, except this time it's now running in the context of the kernel, right? And so once you are able to actually, you know, attack this driver, cause some sort of memory corruption in the kernel, you're on the way to kernel code execution.

The main tool chain moves to BenUtils 2.47, GCC 16.2, and glibc 2.44.

The book now uses Linux kernel 7.1.8, along with Python 3.14.7, Systemd 2.61.2, OpenSSL 4.0.1, core utils 9.11, and a bunch of other updated components.

In total, 46 packages were updated and added since LFS 13.0, and the team says more than 200 commits went into the book between releases.

There are also some security-related updates, but the reason I want to tell you about this is because I like covering Linux from scratch.

All right, so the next one is kind of, ah, seems important.

Ah, the proof concept published for Linux Kernel Privesc, ah, flaw.

And, and I was reading it and I was trying to figure out how the heck could, you know, how hard is it to, to...

How easy is it for somebody to be exploited if they have a Linux box that's on the internet? Turns out they have to have a user account, right?

But I read something, or, or w- there was a story, uh, years ago, I think it was before we started the podcast, where they were talking to Linus Torvald who's the guy who started Linux.

Right.

And they pointed out that there were some problems with the Linux kernel That were architectural-

Hmm

And another thing I find interesting, I find this really fascinating.

This chart right here, represents AI-generated code submissions to the Linux kernel, right? So this is just the Linux kernel and just since February.

We don't really have good numbers for January and before because like mid to late January is when The Linux kernel started doing self-reporting on new patches coming in about whether or not they were AI-generated.

So that's the only period of time we have any sort of real numbers on at all.

But you'll notice something.

I find that fascinating.

I find it fascinating that there are huge numbers of Linux users out there because a lot of the people doing this attacking were Linux users when you go into their bios, like lots of them were, and they were just vulgar and angry about it.

But they're Linux users that are not only attacking people, and vilifying people rather viciously for using AI, but they at the same time are themselves using the Linux kernel, which is over 10% AI vibe coded.