Several Linux kernel vulnerabilities accidentally posted to public mailing list

Doesn't the Linux kernel encourage reporting on the public mailing list for kernel vulnerabilities that were found using AI? If I remember correctly they introduced that policy after the security mailing list got swamped with multiple reports for the same vulnerabilities

Still bleary eyed, but: Most severe ones are in SMB and KSMBD, which apparently have implementations in kernel space. I think this doesn't impact anyone not using KMB.

Others are LPEs, but two have been deleted by now, so can't be sure of the details.

TrendMicro's site opens up with a big big "Advancing AI-Native Security with Anthropic". Which checks out I guess.

The headline should include Trend Micro's name for shaming purposes. Amatuerish.

What an entertaining season in the simulation

Do You guys think that with ai we Will achieve something like a bug free os distro or programming language? Like some sort of perfection?

Someone said that "they" are setting up the narrative for a global tech crash/internet blackout, and it's becoming easier and easier to believe it.

I'm not surprised because the disclosure process of https://hackerone.com is completely and openly public.

But they have also disabled Linux as one of the products that they work with.

It's being a great season, techsecurity-wise.

Finally the last vulnerabilities of the year.

are those posted by AI?

"accidentally"

I feel paranoid enough now to blame ai companies to try to induce panic and proclaim "buy our product to save yourself"

Can we kick SMB implementations out of the kernel please? If not, can we please get PHP mainlined in the kernel?

Is this a parody article?

This is like saying "Linux source code leaked"

[dead]