# SUSE-SU-2025:20844-1: Security update for aaa_base

> An update to aaa_base enforces Yama ptrace restrictions, preventing potential security bypasses related to process tracing on SUSE systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2025

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

SUSE-SU-2025:20844-1 is a vulnerability in aaa_base, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for aaa_base fixes the following issues:

Update to version 84.87+git20240906.742565b:

  * yama-enable-ptrace: enforce changed behavior upon installation (bsc#1221763)
  * Avoid unnecessary /bin/bash dependency
  * sysctl: Fixup of not setting kernel.pid_max on 32b archs (bsc#1227117)

Update to version 84.87+git20240821.fbabe1d:

  * Add helper service for soft-reboot

Update to version 84.87+git20240809.5d13eb4:

  * cleanup aaa_base.post and fold back into specfile

Update to version 84.87+git20240805.7513b28:

  * Remove obsolete resolv+ manual page
  * Remove obsolete defaultdomain.5 manual page
  * Move /etc/skel to /usr/etc/skel (hermetic-usr)
  * Remove obsolete refresh_initrd
  * Add deprecation notice for service [jsc#PED-266]

Update to version 84.87+git20240801.75f05dd:

  * sysctl: Don't set kernel.pid_max on 32b archs (bsc#1227117)

Update to version 84.87+git20240620.57ee9e1:

  * Remove legacy-actions support [jsc#PED-264]

Update to version 84.87+git20240617.f5ff27f:

  * add /usr/bin/nu to etc/shells for nushell

Update to version 84.87+git20240614.332933e:

  * Do not save/restore cursor for foot at status line
  * Add tmux and others to DIR_COLORS (Issue #116)
  * Remove kernel.pid_max limit (bsc#1219038)
  * Add subpackge to enable ptrace

Update to version 84.87+git20240523.10a5692:

  * Add tmpfiles.d/soft-reboot-cleanup.conf

Update to version 84.87+git20240415.e6815bf:

  * drop obsolete 50-default-s390.conf (bsc#1211721)
  * fix typo in alljava.csh and drop stderr redirection

Update to version 84.87+git20240402.16596d1:

  * add alacritty to DIR_COLORS
  * Make sure tput it present before resetting TERM
  * Add mc helpers for both tcsh and bash resources
  * Do not overwrite escape sequences for xterm like
  * Check for valid TERM

Update to version 84.87+git20240202.9526d46:

  * properly shorten the variable when setting JAVA_HOME and JRE_HOME
  * silence output of alljava
  * Restrict ptrace with Yama LSM by default
  * patch alljava.sh and alljava.csh, use the links from update alternatives

Update to version 84.87+git20231023.f347d36:

  * Remove %ghost lastlog entry, lastlog is long gone
  * Remove shaky safe-rm and safe-rmdir helpers (bsc#1159103)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aaa_base` | SUSE:Linux Micro 6.0 | All versions | 84.87+git20240906.742565b-1.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2025:20844-1 is a vulnerability in aaa_base, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2025:20844-1 in the wild and no public exploit code.

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

## Sources

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

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