Описание
Security update for the Linux Kernel RT (Live Patch 3 for SLE 15 SP7)
This update for the Linux Kernel 6.4.0-150700_7_13 fixes several issues.
The following security issues were fixed:
- CVE-2025-38678: netfilter: nf_tables: reject duplicate device on updates (bsc#1249534).
- CVE-2025-38499: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns (bsc#1248673).
- CVE-2025-38566: sunrpc: fix handling of server side tls alerts (bsc#1248376).
- kernel-livepatch.spec: Replace kernel-syms with kernel-<flavor>-specific dependencies (bsc#1248108) The commit ead79afe7cbfae ('kernel-livepatch.spec: Update build dependencies for non-default flavors') broke build of livepatches which were built with kernel-syms-rt. The problem is that livepatch packages for already released kernels are built in exactly the same build environment as the initial livepatch. The BS (Build Service) installs the build environment using the given _buildinfo-*.xml and ignores BuildRequires. But the BuildRequires are later checked by rpmbuild tool. It would complain when new dependencies were added. Unfortunately, kernel-syms-rt does not exist on SLE16. This was the main motivation for the above mentioned commit. But the package kernel-syms is empty. Its only purpose is to add other dependencies. Replace it by opencoding the dependencies. Note that the kernel devel files are historically split into various packages, kernel-<flavor>-devel, kernel-devel-<flavor>, and even kernel-devel. But it is enough to require kernel-<flavor>-devel because it requires the other devel files on its own. This seems to be true back to SLE15-SP4 at minimum.
Список пакетов
SUSE Linux Enterprise Live Patching 15 SP6
SUSE Linux Enterprise Live Patching 15 SP7
Ссылки
- Link for SUSE-SU-2025:03643-1
- E-Mail link for SUSE-SU-2025:03643-1
- SUSE Security Ratings
- SUSE Bug 1248108
- SUSE Bug 1248376
- SUSE Bug 1248673
- SUSE Bug 1249534
- SUSE CVE CVE-2025-38499 page
- SUSE CVE CVE-2025-38566 page
- SUSE CVE CVE-2025-38678 page
Описание
In the Linux kernel, the following vulnerability has been resolved: clone_private_mnt(): make sure that caller has CAP_SYS_ADMIN in the right userns What we want is to verify there is that clone won't expose something hidden by a mount we wouldn't be able to undo. "Wouldn't be able to undo" may be a result of MNT_LOCKED on a child, but it may also come from lacking admin rights in the userns of the namespace mount belongs to. clone_private_mnt() checks the former, but not the latter. There's a number of rather confusing CAP_SYS_ADMIN checks in various userns during the mount, especially with the new mount API; they serve different purposes and in case of clone_private_mnt() they usually, but not always end up covering the missing check mentioned above.
Затронутые продукты
Ссылки
- CVE-2025-38499
- SUSE Bug 1247976
- SUSE Bug 1248673
Описание
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix handling of server side tls alerts Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec.. kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer. This patch proposes to rework how control messages are setup and used by sock_recvmsg(). If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator before calling into the tls_alert_recv.
Затронутые продукты
Ссылки
- CVE-2025-38566
- SUSE Bug 1248374
- SUSE Bug 1248376
Описание
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: reject duplicate device on updates A chain/flowtable update with duplicated devices in the same batch is possible. Unfortunately, netdev event path only removes the first device that is found, leaving unregistered the hook of the duplicated device. Check if a duplicated device exists in the transaction batch, bail out with EEXIST in such case. WARNING is hit when unregistering the hook: [49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S 6.16.0+ #170 PREEMPT(full) [...] [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150
Затронутые продукты
Ссылки
- CVE-2025-38678
- SUSE Bug 1249126
- SUSE Bug 1249534