# SUSE-SU-2025:20617-1: Security update for kernel-livepatch-MICRO-6-0_Update_10

> Initial livepatch for SUSE Micro kernel update 10, addressing unspecified security issues in the operating system kernel.

- **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:** 25 Aug 2025

## What is SUSE-SU-2025:20617-1?

SUSE-SU-2025:20617-1 is a vulnerability in kernel-livepatch-MICRO-6-0_Update_10, published on 25 Aug 2025. 

### Official description

This update for kernel-livepatch-MICRO-6-0_Update_10 fixes the following issues:

This is the initial livepatch for SL Micro 6.0 and 6.1 kernel update 10.

## Which versions are affected by SUSE-SU-2025:20617-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-MICRO-6-0_Update_10` | SUSE:Linux Micro 6.1 | All versions | 1-1.1 |

## How do I fix SUSE-SU-2025:20617-1?

Apply the vendor's patch.

## Is SUSE-SU-2025:20617-1 being exploited?

There is no known exploitation of SUSE-SU-2025:20617-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2025:20617-1 and fix it if it is affected.

What it is: SUSE-SU-2025:20617-1 is a vulnerability in kernel-livepatch-MICRO-6-0_Update_10, published on 25 Aug 2025. 
Exploitation: There is no known exploitation of SUSE-SU-2025:20617-1 in the wild and no public exploit code.

Affected product: kernel-livepatch-MICRO-6-0_Update_10. 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-2025-20617-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20617-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2025:20617-1

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