# openSUSE-SU-2026:21325-1: Security update for cryptsetup

> An attacker with local access could potentially read encrypted volume keys due to improper keyring handling in cryptsetup.

- **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:** 13 Jul 2026

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

openSUSE-SU-2026:21325-1 is a vulnerability in cryptsetup, published on 13 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for cryptsetup fixes the following issues:

Changes in cryptsetup:

- Fix for (bsc#1270254) to avoid undesired pinning of all volume
  keys (via the thread keyring) through the caller's credentials
  when the kernel opens a file. This is due to the refactoring in
  kernel commit a28d893eb327 ("md: port block device access to file")
  that accidentally causes the caller's thread keyring to be kept
  alive long beyond the caller's lifetime, the kernel part is tracked
  in (bsc#1270252).

  * Add keyring key type. [b6fb6fc0]
  * Load volume keys in intermediary keyring linked in thread
    keyring. [413a3dd0]
  * Use unique intermediary keyring name per device. [04ef07a7]
  * Add regression tests. [bfcb0c38, bb5e8e9f, e6573494, aa214c09]

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cryptsetup` | openSUSE:Leap 16.0 | All versions | 2.8.4-160000.2.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2026:21325-1 is a vulnerability in cryptsetup, published on 13 Jul 2026. 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 openSUSE-SU-2026:21325-1 in the wild and no public exploit code.

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

## Sources

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

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