# openSUSE-SU-2026:20124-1: Security update for ucode-amd

> Security update for AMD CPU microcode on openSUSE, addressing unspecified hardware-level vulnerabilities.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 28 Jan 2026

## What is openSUSE-SU-2026:20124-1?

openSUSE-SU-2026:20124-1 is a vulnerability in ucode-amd, published on 28 Jan 2026. 

### Official description

This update for ucode-amd fixes the following issues:

Changes in ucode-amd:

- Update to version 20251203 (git commit a0f0e52138e5):

  * linux-firmware: Update amd-ucode copyright information
  * linux-firmware: Update AMD cpu microcode

- Update to version 20251113 (git commit fb0dbcd30118):

  * linux-firmware: Update AMD cpu microcode

- Update to version 20251031 (git commit 04b323bb64f9):

  * linux-firmware: Update AMD cpu microcode

- Update to version 20251028 (git commit 4f72031fc195):

  * linux-firmware: Update AMD cpu microcode

- Update to version 20251024 (git commit 9b899c779b8a):

  * amd-ucode: Fix minimum revisions in README

- Update to version 20250730 (git commit 910c19074091):

  * linux-firmware: Update AMD cpu microcode

## Which versions are affected by openSUSE-SU-2026:20124-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ucode-amd` | openSUSE:Leap 16.0 | All versions | 20251203-160000.1.1 |

## How do I fix openSUSE-SU-2026:20124-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2026:20124-1 being exploited?

There is no known exploitation of openSUSE-SU-2026:20124-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2026:20124-1 and fix it if it is affected.

What it is: openSUSE-SU-2026:20124-1 is a vulnerability in ucode-amd, published on 28 Jan 2026. 
Exploitation: There is no known exploitation of openSUSE-SU-2026:20124-1 in the wild and no public exploit code.

Affected product: ucode-amd. 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/openSUSE-SU-2026-20124-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20124-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2026:20124-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2026-20124-1/
Summaries are generated and may contain mistakes; the official description above is the record.