Security update for the Linux Kernel RT (Live Patch 4 for SUSE Linux Enterprise 15 SP7) SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:4169-1 Final 1 1 2025-11-22T08:34:35Z current 2025-11-22T08:34:35Z 2025-11-22T08:34:35Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for the Linux Kernel RT (Live Patch 4 for SUSE Linux Enterprise 15 SP7) This update for the SUSE Linux Enterprise kernel 6.4.0-150700.7.16 fixes one security issue The following security issue was fixed: - CVE-2025-38616: tls: handle data disappearing from under the TLS ULP (bsc#1249537). The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-2025-4169,SUSE-SLE-Module-Live-Patching-15-SP7-2025-4169 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-20254169-1/ Link for SUSE-SU-2025:4169-1 https://lists.suse.com/pipermail/sle-security-updates/2025-November/023328.html E-Mail link for SUSE-SU-2025:4169-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1249537 SUSE Bug 1249537 https://www.suse.com/security/cve/CVE-2025-38616/ SUSE CVE CVE-2025-38616 page SUSE Linux Enterprise Live Patching 15 SP7 kernel-livepatch-6_4_0-150700_7_16-rt-4-150700.2.1 kernel-livepatch-6_4_0-150700_7_16-rt-4-150700.2.1 as a component of SUSE Linux Enterprise Live Patching 15 SP7 In the Linux kernel, the following vulnerability has been resolved: tls: handle data disappearing from under the TLS ULP TLS expects that it owns the receive queue of the TCP socket. This cannot be guaranteed in case the reader of the TCP socket entered before the TLS ULP was installed, or uses some non-standard read API (eg. zerocopy ones). Replace the WARN_ON() and a buggy early exit (which leaves anchor pointing to a freed skb) with real error handling. Wipe the parsing state and tell the reader to retry. We already reload the anchor every time we (re)acquire the socket lock, so the only condition we need to avoid is an out of bounds read (not having enough bytes in the socket for previously parsed record len). If some data was read from under TLS but there's enough in the queue we'll reload and decrypt what is most likely not a valid TLS record. Leading to some undefined behavior from TLS perspective (corrupting a stream? missing an alert? missing an attack?) but no kernel crash should take place. CVE-2025-38616 SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_7_16-rt-4-150700.2.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/support/update/announcement/2025/suse-su-20254169-1/ https://www.suse.com/security/cve/CVE-2025-38616.html CVE-2025-38616 https://bugzilla.suse.com/1248512 SUSE Bug 1248512 https://bugzilla.suse.com/1249537 SUSE Bug 1249537