SUSE-SU-2018:1661-1 Security update for ucode-intel
Not scored
Published
Check this codebase for SUSE-SU-2018:1661-1 and fix it if it is affected.
What it is: SUSE-SU-2018:1661-1 is a vulnerability in ucode-intel, published on 12 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2018:1661-1 in the wild and no public exploit code.
Affected product: ucode-intel. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2018-1661-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-1661-1/index.md)
An attacker can exploit Intel CPU microcode vulnerabilities to bypass security features or escalate privileges on affected SUSE systems.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2018:1661-1?
SUSE-SU-2018:1661-1 is a vulnerability in ucode-intel, published on 12 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
This update for ucode-intel fixes the following issues:
Update to version 20180425 (bsc#1091836)
Fix provided for:
GLK B0 6-7a-1/01 0000001e->00000022 Pentium Silver N/J5xxx, Celeron N/J4xxx
Name microcodes which are not allowed to load late with a *.early suffix
Which versions are affected by SUSE-SU-2018:1661-1?
Linux distribution packages (10)
ucode-intel SUSE:Enterprise Storage 4 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server 12 SP3 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server 12-LTSS | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 20180425-13.20.1 |
ucode-intel SUSE:OpenStack Cloud 7 | All versions | 20180425-13.20.1 |
How do I fix SUSE-SU-2018:1661-1?
Apply the vendor's patch.
Is SUSE-SU-2018:1661-1 being exploited?
There is no known exploitation of SUSE-SU-2018:1661-1 in the wild and no public exploit code.