2026-09-29 12:00 UTC
Replies (5)
-
@matt_garber@mastodon.social 2026-09-29 12:43
@fionescu@mastodon.bsd.cafe @peteorrall@mastodon.bsd.cafe @stefano@mastodon.bsd.cafe This is (unfortunately?) due to the Linux kernel developers’ stance of classifying many/most bugs as potential security issues once they became their own CVE numbering authority (CNA). For that process difference alone, it’s a bit hard to compare, even if I’m sure they have been discovering issues much more rapidly over the past year. https://utcc.utoronto.ca/~cks/space/blog/linux/KernelBugfixCVEsAStory
-
@kazord@mamot.fr 2026-09-29 12:57
@fionescu@mastodon.bsd.cafe @peteorrall@mastodon.bsd.cafe @stefano@mastodon.bsd.cafe Hope to find in short future some analysis of : how those vulnerability end up in & how they where found
-
@FrankauLux@mastodon.social 2026-09-29 12:58
@fionescu@mastodon.bsd.cafe @peteorrall@mastodon.bsd.cafe @stefano@mastodon.bsd.cafe yep. Linux is definitely better ! 😜
-
@tfb@mastodon.bsd.cafe 2026-09-29 13:06
@fionescu@mastodon.bsd.cafe This is mostly the Linux kernel devs being weirdos, and only secondarily many things being found by LLMs They're their own CVE issuer, and they refuse to draw a distinction between bugs and security vulnerabilities. Which in one sense, yeah their architecture makes that a difficult distinction to make. On the other hand, crap like this makes it impossible to figure out when they issue a meaningful security fix. @peteorrall@mastodon.bsd.cafe @stefano@mastodon.bsd.cafe
-
@tux0r@layer8.space 2026-09-30 11:55
@fionescu@mastodon.bsd.cafe @peteorrall@mastodon.bsd.cafe @stefano@mastodon.bsd.cafe libexpat is working on that