SUSE-SU-2026:3433-1: low: Security update for runc

[SLE-UPDATES]

# Security update for runc

Announcement ID: SUSE-SU-2026:3433-1  
Release Date: 2026-07-30T18:54:54Z  
Rating: low  
References:

  * bsc#1268275

  
Cross-References:

  * CVE-2026-41579

  
CVSS scores:

  * CVE-2026-41579 ( SUSE ):  3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
  * CVE-2026-41579 ( NVD ):  3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

  
Affected Products:

  * Basesystem Module 15-SP7
  * SUSE Enterprise Storage 7.1
  * SUSE Linux Enterprise Desktop 15 SP7
  * SUSE Linux Enterprise Micro 5.3
  * SUSE Linux Enterprise Micro 5.4
  * SUSE Linux Enterprise Micro 5.5
  * SUSE Linux Enterprise Micro for Rancher 5.3
  * SUSE Linux Enterprise Micro for Rancher 5.4
  * SUSE Linux Enterprise Real Time 15 SP7
  * SUSE Linux Enterprise Server 15 SP3
  * SUSE Linux Enterprise Server 15 SP7
  * SUSE Linux Enterprise Server for SAP Applications 15 SP7

  
  
An update that solves one vulnerability can now be installed.

## Description:

This update for runc fixes the following issues:

Update to 1.3.6.

  * CVE-2026-41579: malicious image with a `/dev` symlink can trigger limited
    host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  * Version 1.3.6:
  * When masking directories with `maskPaths`, runc will now re- use a single
    `tmpfs` instance (which is not writeable) to reduce the number `tmpfs`
    superblocks that need to be reaped when containers die (in particular,
    Kubernetes applies masks to per-CPU sysfs directories which get expensive
    quickly).
  * Version 1.3.5:
  * Recursive atime-related mount flags (rrelatime et al.) are now applied
    properly.
  * PR #4757 caused a regression that resulted in spurious cannot start a
    container that has stopped errors when running runc create and has thus been
    reverted.
  * Updated builds to Go 1.25, libseccomp v2.6.0.
  * Minor signing keyring updates.

## Patch Instructions:

To install this SUSE update use the SUSE recommended installation methods like
YaST online_update or "zypper patch".  
Alternatively you can run the command listed for your product:

  * SUSE Linux Enterprise Micro for Rancher 5.4  
    zypper in -t patch SUSE-SLE-Micro-5.4-2026-3433=1

  * SUSE Linux Enterprise Micro 5.4  
    zypper in -t patch SUSE-SLE-Micro-5.4-2026-3433=1

  * SUSE Linux Enterprise Micro 5.5  
    zypper in -t patch SUSE-SLE-Micro-5.5-2026-3433=1

  * SUSE Linux Enterprise Micro for Rancher 5.3  
    zypper in -t patch SUSE-SLE-Micro-5.3-2026-3433=1

  * SUSE Linux Enterprise Micro 5.3  
    zypper in -t patch SUSE-SLE-Micro-5.3-2026-3433=1

  * Basesystem Module 15-SP7  
    zypper in -t patch SUSE-SLE-Module-Basesystem-15-SP7-2026-3433=1

  * SUSE Enterprise Storage 7.1  
    zypper in -t patch SUSE-Storage-7.1-2026-3433=1

## Package List:

  * SUSE Linux Enterprise Micro 5.5 (aarch64 ppc64le s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * SUSE Linux Enterprise Micro for Rancher 5.4 (aarch64 s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * SUSE Linux Enterprise Micro 5.4 (aarch64 s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * Basesystem Module 15-SP7 (aarch64 ppc64le s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * SUSE Linux Enterprise Micro for Rancher 5.3 (aarch64 s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * SUSE Linux Enterprise Micro 5.3 (aarch64 s390x x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1
  * SUSE Enterprise Storage 7.1 (aarch64 x86_64)
    * runc-1.3.6-150000.101.1
    * runc-debuginfo-1.3.6-150000.101.1

## References:

  * https://www.suse.com/security/cve/CVE-2026-41579.html
  * https://bugzilla.suse.com/show_bug.cgi?id=1268275

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/sle-updates/attachments/20260731/33afa9e7/attachment.htm>