I am assuming that many of these are found with automatic analysis tools that are very creative (i.e. LLMs) and there may be a high proportion of very "cornered" cases. I think there needs to be a triage method that would amount to the severity, likeliness, and detection dimensions used to rank risks in a systematic framework [1]. I think if this could be submitted (or estimated) along with such bug reports, it could…
In my company, the security team isn’t technical. They see CVE, find a vulnerable system, it gets flagged. We have to patch it. We patched for a CVE last week that a malicious usb sound card device could be use the gain root. On a Vm? Is that something we really need to worry about??
Over 400 Linux CVEs published in the last 24 hours alone
21–30 of 52 posts
Re: Over 400 Linux CVEs published in the last 24 hours alone
#22Re: Over 400 Linux CVEs published in the last 24 hours alone
#23I am assuming that many of these are found with automatic analysis tools that are very creative (i.e. LLMs) and there may be a high proportion of very "cornered" cases. I think there needs to be a triage method that would amount to the severity, likeliness, and detection dimensions used to rank risks in a systematic framework [1]. I think if this could be submitted (or estimated) along with such bug reports, it could…
> Note, due to the layer at which the Linux kernel is in a system, almost any bug might be exploitable to compromise the security of the kernel, but the possibility of exploitation is often not evident when the bug is fixed. Because of this, the CVE assignment team is overly cautious and assign CVE numbers to any bugfix that they identify. This explains the seemingly large number of CVEs that are issued by the Linux kernel team.
Re: Over 400 Linux CVEs published in the last 24 hours alone
#24Earlier quoted context omitted.
In my company, the security team isn’t technical. They see CVE, find a vulnerable system, it gets flagged. We have to patch it. We patched for a CVE last week that a malicious usb sound card device could be use the gain root. On a Vm? Is that something we really need to worry about??
[flagged]
Most businesses run on a, "least to be in compliance" model.
Re: Over 400 Linux CVEs published in the last 24 hours alone
#25Chinese models, hurray!
Re: Over 400 Linux CVEs published in the last 24 hours alone
#26Go Greg!!
Re: Over 400 Linux CVEs published in the last 24 hours alone
#27Re: Over 400 Linux CVEs published in the last 24 hours alone
#28I am assuming that many of these are found with automatic analysis tools that are very creative (i.e. LLMs) and there may be a high proportion of very "cornered" cases. I think there needs to be a triage method that would amount to the severity, likeliness, and detection dimensions used to rank risks in a systematic framework [1]. I think if this could be submitted (or estimated) along with such bug reports, it could…
Re: Over 400 Linux CVEs published in the last 24 hours alone
#29Might need to silently archive those Microsoft Patch Tuesday jokes...
Also, if Microsoft hypothetically open sourced their code, do you think there would be more, less, or the same number of CVEs? I would guess more.
I don't want to go too far to defend Linux. I want to make the case that it has been the more secure OS this whole time.
Re: Over 400 Linux CVEs published in the last 24 hours alone
#30Earlier quoted context omitted.
In my company, the security team isn’t technical. They see CVE, find a vulnerable system, it gets flagged. We have to patch it. We patched for a CVE last week that a malicious usb sound card device could be use the gain root. On a Vm? Is that something we really need to worry about??
[flagged]
There were plenty of even less useful flags, but that one stood out to me for some reason.
"Checklist security" has been a thing for ages.