Posts
441
Following
100
Followers
4748
gregkh

Greg K-H

Reply to @m_berberich@chaos.social
@m_berberich Adding a backdoor by reporting a bug without a patch? That seems like a very tough injection method :)
2
0
4
gregkh

Greg K-H

Reply to @aho@mastodon.social
@aho maybe, but at least one reporter insisted it wasn't LLM generated, which of course does not actually make it true, and pointed instead at a 10 year old presentation that they "happened" to find.
2
0
3
gregkh
repeated
sjvn@mastodon.social

sjvn

Close enough.

1
6
0
gregkh

Greg K-H

We've gotten five different "security reports" about the decades old USBIP protocol https://docs.kernel.org/usb/usbip_protocol.html and how it is "insecure" in the past few days.

Yes, it's only to be run between "trusted" devices, and we will gladly take patches so see the ones recently posted to the linux-usb mailing list to mitigate these issues, but this is very strange as to why all of a sudden this is being reported all at the same time by random different semi-anonymous accounts.

Is there some big usb-over-ip installation somewhere that people suddenly started caring about out there, or did some internal hacking tool that uses usbip just get leaked?

No one who we asked "why?" when they submitting these issues would give a very clear answer to that simple question so something is going on...
8
37
40
gregkh
repeated
joshbressers@infosec.exchange

Josh Bressers

Reply to @bagder@mastodon.social

@bagder @gregkh @hanno

Probably add @sjvn to this

Finding vulnerabilities in code is something humans are bad at. There are a few that are good (like Hanno), but I would say in general it's not a common skill

So the bar for LLMs to find vulnerabilities is very very low

1
1
1
gregkh

Greg K-H

Reply to @richlv@mastodon.social
@richlv @hanno Given that they have not been "found" yet by other tools that we know of, I would guess no. It's just "fuzzy pattern matching" which to be fair, is what LLMs are actually good at doing.
1
0
1
gregkh

Greg K-H

Reply to @hanno@mastodon.social
@hanno It is real, see my interview in the Register today about this very problem: https://www.theregister.com/2026/03/26/greg_kroahhartman_ai_kernel/
2
14
20
gregkh
repeated
mechko@chaos.social

Mirko Swillus

Reply to @mechko@chaos.social

Link (feedback possible until March 31): https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/16959-Draft-Commission-guidance-on-the-Cyber-Resilience-Act_en

0
1
0
gregkh
repeated
mechko@chaos.social

Mirko Swillus

Edited 3 months ago

This week the European Commission published the draft for a guidance document for the Cyber Resilience Act (CRA). It is 70 pages, but contains some helpful examples and flowcharts, like this one, making it accessible even to Open Source folks with limited time.

Here: Quick guidance for the question if your FOSS component is in scope for the CRA, and if so, wether you're deemed a steward or manufacturer in regards of the component.

2
12
0
gregkh

Greg K-H

Reply to @musicmatze@social.linux.pizza
@musicmatze Yes, I use b4 a lot, it's very helpful. And one of these days I'll document my patch workflow again, it is be behind many other things I "should" be writing about :)
1
0
3
gregkh

Greg K-H

Reply to
@wagi https://git.sr.ht/~gregkh/presentation-cra/tree is a link to my CRA presentations, but I don't know about any "tool to check CRA compliance" that is out there.

For a steward, you only have to do 2 things, so should I just make a checklist with those 2 things on it for people to use? :)
0
0
1
gregkh

Greg K-H

After talking with a bunch of different companies / groups, we've now bumped the length of a few of the longterm kernels we are supporting:
https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=d04587da86a3464881e0c97aabddd2c271105698

As always, the dates can be found at:https://www.kernel.org/category/releases.html
2
21
36
gregkh
repeated
monsieuricon

K. Ryabitsev-Prime 🍁

Gemini, please convert this response into a politely worded email:

Hi:

Your vulnerability report is stupid. You have no idea what you're talking about, or you're hoping that nobody actually checks your findings. Unfortunately for me, I did check your findings and I will never get these 20 minutes of my life back. Everyone is dumber as a result of your report. Please do not contact us again.
3
15
69
gregkh

Greg K-H

Reply to @T_X@chaos.social
@T_X according to cve.org, nope, sorry. Take it up with them if you don't agree, I don't write the rules here (hint, I think backups should have been involved somewhere...)
0
0
0
gregkh

Greg K-H

Reply to @T_X@chaos.social
@T_X @awlnx "sophisticated USB storage devices " can do loads of horrible things to your system. Linux (and all other operating systems) trust the hardware not to do dumb/bad/foolish things like that. If you don't trust the hardware, don't plug it in. That's what USBGuard is for, a protection for you to make the decision to trust the device or not, that's not something that the kernel can decide for you.
0
0
1
gregkh

Greg K-H

It was one of those Mondays...

https://lwn.net/Articles/1059031/
3
6
27
gregkh

Greg K-H

Reply to @joshbressers@infosec.exchange
@joshbressers The version question/range is a good one, it requires a solid and long description of the problem and why it's required, with real examples. A response here isn't going to be sufficient, I'll work on that as the "next" post in this series.

For "why we we provide CPE", we provide it because some groups were "adding" CPE data that was flat out wrong because our records did not have any values. By providing the "real" CPE description, according to their specification, that mostly prevents that from happening.

CPE on its own, doesn't actually give you enough information to properly determine a "am I vulnerable" question giving a release that someone is currently on, as you well know. I guess it's good enough to search on "linux*" to filter that way :)

Hopefully PURL will help out a lot here, I have hope...
0
0
1
gregkh

Greg K-H

Another post in my series about the kernel CVE process, all about how we classify fixes to be assigned a CVE and other related things:

http://www.kroah.com/log/blog/2026/02/16/linux-cve-assignment-process/
3
21
38
gregkh
repeated
jamie@zomglol.wtf

Jamie Gaskins

If you use AI-generated code, you currently cannot claim copyright on it in the US. If you fail to disclose/disclaim exactly which parts were not written by a human, you forfeit your copyright claim on *the entire codebase*.

This means copyright notices and even licenses folks are putting on their vibe-coded GitHub repos are unenforceable. The AI-generated code, and possibly the whole project, becomes public domain.

Source: https://www.congress.gov/crs_external_products/LSB/PDF/LSB10922/LSB10922.8.pdf

4
37
1
gregkh

Greg K-H

Reply to
@n0toose @bagder @hughsie @Stephanie Of course, public fixes for public bugs is the huge percentage (like 99%) of all of our security fixes that end up getting accepted and later assigned a CVE.
0
0
1
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: