Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @dalias@hachyderm.io
Jan Schaumann@jschauma@mstdn.social (2026-09-29 22:18:16)
@dalias Yep.  It's the kernel team's decision to assign a CVE ID to just about any change. Combined with the onslaught of AI findings, this gets us to thousands of CVEs, and trying to assess which, if any, are meaningful and affect your particular stack and configuration is, IMO, no longer possible.
---Reply---
Cassandrich@dalias@hachyderm.io (2026-09-29 22:19:26)
@jschauma Because the kernel team is actively promoting the slopbros' agenda. 🤬

---Replies---

khm@khm@hj.9fs.net (2026-09-29 22:31:52)
this predates the advent of slopcoding -- greg kh has long been angry that someone else has opinions about kernel bugs, and deliberately spams the cve lists explicitly to promote the "you should just uncritically update to whatever greg kh says" response.

it's a bad faith participation only possible because MITRE completely abdicated managerial control of the program

CC: @jschauma@mstdn.social