Please update microcode for 06-5e-03
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux
- Domain
- operating-systems, security
Research direction
Start with /lib/firmware/intel-ucode/06-5e-03.initramfs and the reported intel-microcode package version. Use iucode-tool to inspect the 0x000506e3 entry, then compare its revision with the GDS requirement shown by /sys/devices/system/cpu/vulnerabilities/gather_data_sampling and dmesg. Done means the CPU receives a suitable microcode revision and no longer reports “Vulnerable: No microcode”.
Written by the indexing model from the issue text.
Description
Hi, using the latest microcode, I'm still vulnerable to GDS.
Here is my CPU and microcode information:
root@gpmd:~# grep -r Vulnerable /sys/devices/system/cpu/vulnerabilities/
/sys/devices/system/cpu/vulnerabilities/gather_data_sampling:Vulnerable: No microcode
root@gpmd:~# dmesg
[ 0.194670] smpboot: CPU0: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (family: 0x6, model: 0x5e, stepping: 0x3)
[ 0.155725] GDS: Vulnerable: No microcode
[ 0.791740] microcode: Current revision: 0x000000f0
[ 0.791752] microcode: Updated early from: 0x00000033
root@gpmd:~# dpkg -l intel-microcode
ii intel-microcode 3.20250211.1 amd64 Processor microcode firmware for Intel CPUs
root@gpmd:~# iucode-tool -l /lib/firmware/intel-ucode/06-5e-03.initramfs
microcode bundle 1: /lib/firmware/intel-ucode/06-5e-03.initramfs
selected microcodes:
001/001: sig 0x000506e3, pf_mask 0x36, 2021-11-12, rev 0x00f0, size 109568
- Dominant language
- No language data
- Stars
- 826
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/Intel-Linux-Processor-Microcode-Data-Files
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
intel/Intel-Linux-Processor-Microcode-Data-Files#112 · 36 comments · 22 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
intel/Intel-Linux-Processor-Microcode-Data-Files#109 · 6 comments · 2 reactions ·
-
Microcode not foundOpen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
intel/Intel-Linux-Processor-Microcode-Data-Files#108 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
intel/Intel-Linux-Processor-Microcode-Data-Files#107 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
intel/Intel-Linux-Processor-Microcode-Data-Files#106 · 1 comment · 1 reaction ·
All issues in intel/Intel-Linux-Processor-Microcode-Data-Files
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetone/magpie#3737 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
raspberrypi/linux#7718 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
sameerasw/essentials#1579 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day