Security update for warewulf4 SUSE Patch security@suse.de SUSE Security Team openSUSE-SU-2025-20031-1 Final 1 1 2025-10-27T09:58:12Z current 2025-10-27T09:58:12Z 2025-10-27T09:58:12Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for warewulf4 This update for warewulf4 fixes the following issues: Changes in warewulf4: - Update to version 4.6.4: * v4.6.4 release updates * Convert disk booleans from wwbool to *bool which allows bools in disk to be set to false via command line (bsc#1248768) * Update NetworkManager Overlay * Disable ipv4 in NetworkManager if no address or route is specified * fix(wwctl): Create overlay edit tempfile in tmpdir * Add default for systemd name for warewulf in warewulf.conf * Atomic overlay file application in wwclient * Simpler names for overlay methods * Fix warewulfd api behavior when deleting distribution overlay - Update to version 4.6.3: * v4.6.3 release * IPv6 iPXE support * Fix a syntax error in the RPM specfile * Fix a race condition in wwctl overlay edit * Fixed handling of comma-separated mount options in `fstab` and `ignition` overlays * Move reexec.Init() to beginning of wwctl * Add documentation for using tmpfs to distribute across numa nodes * added warewuld configure option * Fix wwctl upgrade nodes to handle kernel argument lists (bsc#1227686 bsc#1227465) * Address copilot review from #1945 * Refactor wwapi tests for proper isolation * Bugfix: cloning a site overlay when parent dir does not exist * Clone to a site overlay when adding files in wwapi * Consolidated createOverlayFile and updateOverlayFile to addOverlayFile * Support for creating and updating overlay file in wwapi * Only return overlay files that refer to a path within the overlay * add overlay file deletion support * DELETE /api/overlays/{id}?force=true can delete overlays in use * Restore idempotency of PUT /api/nodes/{id} * Simplify overlay mtime api and add tests * add node overlay buildtime * Improved netplan support * Rebuild overlays for discovered nodes * Restrict userdocs from building during pr when not modified * Update to v4.6.2 GitHub release notes The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). openSUSE-Leap-16.0-packagehub-7 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1227465 SUSE Bug 1227465 https://bugzilla.suse.com/1227686 SUSE Bug 1227686 https://bugzilla.suse.com/1246082 SUSE Bug 1246082 https://bugzilla.suse.com/1248768 SUSE Bug 1248768 https://bugzilla.suse.com/1248906 SUSE Bug 1248906 https://www.suse.com/security/cve/CVE-2025-58058/ SUSE CVE CVE-2025-58058 page openSUSE Leap 16.0 warewulf4-4.6.4-bp160.1.1 warewulf4-dracut-4.6.4-bp160.1.1 warewulf4-man-4.6.4-bp160.1.1 warewulf4-overlay-4.6.4-bp160.1.1 warewulf4-overlay-rke2-4.6.4-bp160.1.1 warewulf4-overlay-slurm-4.6.4-bp160.1.1 warewulf4-reference-doc-4.6.4-bp160.1.1 warewulf4-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-dracut-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-man-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-overlay-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-overlay-rke2-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-overlay-slurm-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 warewulf4-reference-doc-4.6.4-bp160.1.1 as a component of openSUSE Leap 16.0 xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14. CVE-2025-58058 openSUSE Leap 16.0:warewulf4-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-dracut-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-man-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-overlay-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-overlay-rke2-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-overlay-slurm-4.6.4-bp160.1.1 openSUSE Leap 16.0:warewulf4-reference-doc-4.6.4-bp160.1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/security/cve/CVE-2025-58058.html CVE-2025-58058 https://bugzilla.suse.com/1248889 SUSE Bug 1248889