3 ms·

Mostly. If this is the same thing that was posted in the last month or so, then it's possible for it be patched. Whether it's the firmware itself or through a m

Mostly. If this is the same thing that was posted in the last month or so, then it's possible for it be patched. Whether it's the firmware itself or through a mitigation technique in the OS, I can't remember. The last time it was posted, it was mostly about phones, and there was an update for Android phones that "fixed" the bug. The status of the bug on iOS was unknown. It may be that the bug is easily defendable against at the OS level if one knows that it could be present. Edit: Somebody else posted the previous discussion, so I think it's the bug I'm thinking of.

deleted 9y ago
[deleted]
deleted 9y ago
[deleted]
ajross 9y ago
In general the firmware for these devices is loaded by the OS at startup, so the OS simply patches the firmware file. Checking the linux-firmware tree for what I presume to be the same devices, though, I see a few recent commits to a handful of files, but nothing that looks like it might be a fix to this issue: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/brcm https://git.kernel.org/pub/scm/linux/kernel/git/firmware/lin...