The problem, as I described in another comment, is that the average programmer doesn't know enough about colour spaces, and sometimes must choose a colour profile while not knowing nor understanding what they actually want. They can figure out that an "sRGB" profile is probably what they want, but then there should not be such a plethora of different versions of that, as choosing between them is impossible for anyone not in the know.
I would have loved to have found this page back when I was adapting some PDF-generating program to conform to PDF/A (which requires a colour profile in some cases). I found several sRGB profiles and could see that they were different, but knowing almost nothing about them I just chose the one that seemed to be from the most authoritative source (I forgot which). This page must have existed then, actually.
True, but the site is called Evil Genius Labs for a reason. And it's not too hard to switch off, there's a clear prompt in the bottom right corner. (Didn't try mobile.)
> ... there's a clear prompt in the bottom right corner.
Indeed, it does.
> (Didn't try mobile.)
And my eyes didn't make it that far down the screen. If i can't read the first paragraph, there's no point in scanning further down the page (and certainly not to look for something as esoteric as an option to disable what should not be there in the first place). Grumble, grumble.
The kernel maintainers don't flag "security fixes" as special, and they have a well-thought-out reason for that, see many other comments in this thread.
That, and they flag pretty much any random patch with a CVE these days, making it harder for distro maintainers to keep up.
For this specific "bug" they took care to not mention any security angle in the commit message, making it extremely hard for an outsider to even realize this was a critical patch. I assume this was because they wanted to push the fix without breaking embargo.
reply