friendica.eskimo.com

Intel Linux Patch Would Report Outdated CPU Microcode As A Security Vulnerability

125 2 1
The Linux kernel would maintain a list of the latest Intel microcode versions for each CPU family, which is based on the data from the Intel microcode GitHub repository. In turn this list would need to be kept updated with new Linux kernel releases and as Intel pushes out new CPU microcode files.


Sounds like that would be outdated for everyone without a rolling distro.

4 3 1
Stable distros can and will backport security fixes. Good ones that is.
10 1
Yeah, methinks this will be one of those alerts pretty much everyone will be like "yeah, yeah, I know" and click to silence those notifications.
1 1
Sounds like a user space application, there's no place for this in the kernel. So would you need to upgrade kennel and reboot to update the list? Nonsense.
This entry was edited (5 months ago)
2 1
If that's the case, why wouldn't they put the microcode in the kernel?
1
@DaPorkchop_ Oddly, if you build your own kernel and remove the system provided one, the package gets automatically removed as well which is weird, because it is really still needed regardless.
1
@ryannathans Why bloat the kernel with the microcode for every intel processor that might need it (and there is a similar thing for AMD) when you don't have that specific processor? It does make more sense for it to be a separate, especially on memory constrained systems. I mean if you've got 256GB of RAM probably not a big deal but if you've got 256MB a big deal.
1

How about a Linux Patch that reports binary blobs wirh no source AS __ Security Vulnerabilities __

Or are we not allowed to criticize the back doors that hackers gain access to.

13 1 1
So the patch is just copying the existing warning to a standard location?
1 1

The kernel compilation is already configurable between megabytes and gigabyte+

Distros pick their featureset

This entry was edited (5 months ago)
1