Mastodawn

Microcode firmware update renders charging to stop #microcode

Microcode firmware update renders charging to stop

Here is a list of problems with Microcode firmware update (latest 11/june/2025) 1)Charging stops 2)Ubuntu 24.04 battery runs down 3)Microcode package rollback may not be possible 4) BIOS updates re...

Ask Ubuntu

Benjamin Carr, Ph.D. 👨🏻‍💻🧬May 14

World's first #CPU-level #ransomware can "bypass every freaking traditional technology we have out there" — new #firmware-based attacks could usher in new era of unavoidable ransomware
Beek, #Rapid7's senior director of threat analytics, revealed AMD Zen chip bug gave him idea that highly skilled attacker could in theory "allow those intruders to load unapproved #microcode into the processors, breaking encryption at the hardware level and modifying CPU behavior at will."
https://www.tomshardware.com/pc-components/cpus/worlds-first-cpu-level-ransomware-can-bypass-every-freaking-traditional-technology-we-have-out-there-new-firmware-based-attacks-could-usher-in-new-era-of-unavoidable-ransomware

World's first CPU-level ransomware can "bypass every freaking traditional technology we have out there" — new firmware-based attacks could usher in new era of unavoidable ransomware

A cybersecurity expert has created a proof of concept for CPU ransomware.

Tom's Hardware

Sean Fenian May 12

https://www.theregister.com/2025/05/11/cpu_ransomware_rapid7/

Spoiler alert: Beek followed through and wrote proof-of-concept code for #ransomware that hides in the computer's #processor. "Of course, we won't release that, but it's fascinating, right?"

This, according to Beek, is the worst-case scenario. "Ransomware at the #CPU level, #microcode alteration, and if you are in the CPU or the #firmware, you will bypass every freaking traditional [anti-malware] technology we have out there."

You think ransomware is bad now? Wait until it infects CPUs

RSAC: Rapid7 threat hunter wrote a PoC. No, he's not releasing it

The Register

Verfassungklage@troet.cafe May 12

Von #AMD-Lücke inspiriert:

#Forscher warnt vor #Ransomware im #CPU-Microcode

Eine Lücke in #AMD-CPUs ermöglicht manipulative Eingriffe in den #Microcode. Darin eingeschleuste #Ransomware wäre äußerst schwer zu bezwingen.

Eine #Ransomware-Infektion kann für Unternehmen weitreichende Folgen haben, die nicht selten auch in einer Insolvenz münden. Durch geeignete Maßnahmen lassen sich die Risiken für solche #Sicherheitsvorfälle eindämmen.

https://www.golem.de/news/von-amd-luecke-inspiriert-forscher-warnt-vor-ransomware-im-cpu-microcode-2505-196112.html

Von AMD-Lücke inspiriert: Forscher warnt vor Ransomware im CPU-Microcode - Golem.de

Eine Lücke in AMD-CPUs ermöglicht manipulative Eingriffe in den Microcode. Darin eingeschleuste Ransomware wäre äußerst schwer zu bezwingen.

Golem.de

Aptivi Apr 22

Linux 6.16 will warn users about outdated Intel microcode

Intel is routinely releasing new microcode for their processors to improve the processor’s performance and to fix critical issues, especially when dealing with security vulnerabilities that may be found in old microcode versions. This is to ensure that your system becomes more secure than before by eliminating security vulnerabilities.

A patch has been queued to the Linux kernel tip repository that will make its way to the Linux 6.16 kernel. It warns the user on boot that the microcode version for the processor is old and that it needs to be updated to ensure security. Userspace applications can determine whether your computer is using the old microcode via the /sys/devices/system/cpu/vulnerabilities/old_microcode file.

The kernel, if running in the old microcode, will be tainted with the TAINT_CPU_OUT_OF_SPEC flag, making it more difficult for kernel bugs that have to do with the old microcode to be reported directly to the bug tracker. The implementation relies on a manually-maintained list of processors found in the intel-ucode-defs.h file. It contains a list of structures that contain the following variables:

flags: List of flags (always X86_CPU_ID_FLAG_ENTRY_VALID)
vendor: Processor vendor (always X86_VENDOR_INTEL)
family: Processor family (usually 0x6 or 0xf)
model: Processor model
steppings: Processor stepping
driver_data: Processor microcode ID as an integer

Not only that, but all processors that are running on a debug microcode (that is, microcode ID with the 31st bit set to 1) are considered to be old.

We advise you to update your processor’s microcode to the latest version to ensure that there are no security vulnerabilities present.

#intel #Kernel #Linux #LinuxKernel #Microcode #news #processor #processors #Tech #Technology #update

Making sure you're not a bot!

N-gated Hacker News Apr 9

🤡 Ah yes, because rewriting #microcode to run #RISC-V on #AMD #CPUs is *definitely* something everyone has on their weekend to-do list. 🛠️ What's next, trying to make a toaster run Crysis? 💡
https://rvspoc.org/en/S2502/ #weekendprojects #techhumor #toastergaming #HackerNews #ngated

Run RISC-V Binaries on AMD Zen-series CPUs via Microcode Modification | RVSPOC 2025

This challenge requires participants to modify microcode on AMD Zen-series CPUs to natively execute RISC-V binaries or accelerate RISC-V binary execution.

Hacker News Apr 9

Run RISC-V Binaries on AMD Zen-Series CPUs via Microcode Modification

https://rvspoc.org/en/S2502/

#HackerNews #RISC-V #AMD #Microcode #Zen-Series #Binaries #Technology

Run RISC-V Binaries on AMD Zen-series CPUs via Microcode Modification | RVSPOC 2025

This challenge requires participants to modify microcode on AMD Zen-series CPUs to natively execute RISC-V binaries or accelerate RISC-V binary execution.

Show thread

boredsquirrel Apr 3

@nixCraft

#NixOS is interesting. Pretty reliable (not as much as #AtomicDesktops in my noob tests) while also performant

Note that such old hardware will have #microcode vulnerabilities and locking it down will further slow it down. At least thinking of #spectre or #meltdown (not sure if hyperthreading was even thought of back then)