# SUSE-SU-2025:20042-1: Security update for selinux-policy

> An attacker could exploit SELinux policy misconfigurations to bypass security controls or escalate privileges on SUSE Linux systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2025

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

SUSE-SU-2025:20042-1 is a vulnerability in selinux-policy, published on 3 Feb 2025. 

### Official description

This update for selinux-policy fixes the following issues:

Update to version 20230523+git25.ad22dd7f:

* Backport wtmpdb label change to have the same wtmpdb label
  as in SL Micro 6.1 (bsc#1229132)
* Add auth_rw_wtmpdb_login_records to domains using auth_manage_login_records
* Add auth_rw_wtmpdb_login_records to modules
* Allow xdm_t to read-write to wtmpdb (bsc#1225984)
* Introduce types for wtmpdb and rw interface
* Introduce wtmp_file_type attribute
* Revert "Add policy for wtmpdb (bsc#1210717)"

Update to version 20230523+git18.f44daf8a:

* Provide type for sysstat lock files (bsc#1228247)

Update to version 20230523+git16.0849f54c:

* allow firewalld access to /dev/random and write HW acceleration logs
  (bsc#1215405, bsc#1227930)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `selinux-policy` | SUSE:Linux Micro 6.0 | All versions | 20230523+git25.ad22dd7f-1.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2025:20042-1 is a vulnerability in selinux-policy, published on 3 Feb 2025. 
Exploitation: There is no known exploitation of SUSE-SU-2025:20042-1 in the wild and no public exploit code.

Affected product: selinux-policy. 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-20042-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20042-1/index.md)
```

## Sources

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

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