<div class="container">
<h1>Security update for cryptsetup</h1>
<table class="table table-striped table-bordered">
<tbody>
<tr>
<th>Announcement ID:</th>
<td>SUSE-SU-2026:22645-1</td>
</tr>
<tr>
<th>Release Date:</th>
<td>2026-07-13T16:23:16Z</td>
</tr>
<tr>
<th>Rating:</th>
<td>moderate</td>
</tr>
<tr>
<th>References:</th>
<td>
<ul>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1270252">bsc#1270252</a>
</li>
<li style="display: inline;">
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1270254">bsc#1270254</a>
</li>
</ul>
</td>
</tr>
<tr>
<th>Affected Products:</th>
<td>
<ul class="list-group">
<li class="list-group-item">SUSE Linux Enterprise Server 16.0</li>
<li class="list-group-item">SUSE Linux Enterprise Server for SAP applications 16.0</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p>An update that has two fixes can now be installed.</p>
<h2>Description:</h2>
<p>This update for cryptsetup fixes the following issues:</p>
<p>Changes in cryptsetup:</p>
<ul>
<li>
<p>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).</p>
</li>
<li>
<p>Add keyring key type. [b6fb6fc0]</p>
</li>
<li>Load volume keys in intermediary keyring linked in thread
keyring. [413a3dd0]</li>
<li>Use unique intermediary keyring name per device. [04ef07a7]</li>
<li>Add regression tests. [bfcb0c38, bb5e8e9f, e6573494, aa214c09]</li>
</ul>
<h2>Patch Instructions:</h2>
<p>
To install this SUSE update use the SUSE recommended
installation methods like YaST online_update or "zypper patch".<br/>
Alternatively you can run the command listed for your product:
</p>
<ul class="list-group">
<li class="list-group-item">
SUSE Linux Enterprise Server 16.0
<br/>
<code>zypper in -t patch SUSE-SLES-16.0-1229=1</code>
</li>
<li class="list-group-item">
SUSE Linux Enterprise Server for SAP applications 16.0
<br/>
<code>zypper in -t patch SUSE-SLES-16.0-1229=1</code>
</li>
</ul>
<h2>Package List:</h2>
<ul>
<li>
SUSE Linux Enterprise Server for SAP applications 16.0 (ppc64le x86_64)
<ul>
<li>cryptsetup-debugsource-2.8.4-160000.2.1</li>
<li>cryptsetup-2.8.4-160000.2.1</li>
<li>libcryptsetup12-2.8.4-160000.2.1</li>
<li>cryptsetup-ssh-debuginfo-2.8.4-160000.2.1</li>
<li>cryptsetup-ssh-2.8.4-160000.2.1</li>
<li>libcryptsetup-devel-2.8.4-160000.2.1</li>
<li>cryptsetup-debuginfo-2.8.4-160000.2.1</li>
<li>libcryptsetup12-debuginfo-2.8.4-160000.2.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server for SAP applications 16.0 (noarch)
<ul>
<li>cryptsetup-doc-2.8.4-160000.2.1</li>
<li>cryptsetup-lang-2.8.4-160000.2.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server 16.0 (noarch)
<ul>
<li>cryptsetup-doc-2.8.4-160000.2.1</li>
<li>cryptsetup-lang-2.8.4-160000.2.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server 16.0 (aarch64 ppc64le s390x x86_64)
<ul>
<li>cryptsetup-debugsource-2.8.4-160000.2.1</li>
<li>cryptsetup-2.8.4-160000.2.1</li>
<li>cryptsetup-ssh-debuginfo-2.8.4-160000.2.1</li>
<li>libcryptsetup12-2.8.4-160000.2.1</li>
<li>cryptsetup-ssh-2.8.4-160000.2.1</li>
<li>libcryptsetup-devel-2.8.4-160000.2.1</li>
<li>cryptsetup-debuginfo-2.8.4-160000.2.1</li>
<li>libcryptsetup12-debuginfo-2.8.4-160000.2.1</li>
</ul>
</li>
</ul>
<h2>References:</h2>
<ul>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1270252">https://bugzilla.suse.com/show_bug.cgi?id=1270252</a>
</li>
<li>
<a href="https://bugzilla.suse.com/show_bug.cgi?id=1270254">https://bugzilla.suse.com/show_bug.cgi?id=1270254</a>
</li>
</ul>
</div>