Описание
Security update for the Linux Kernel (Live Patch 38 for SUSE Linux Enterprise 15 SP4)
This update for the SUSE Linux Enterprise Kernel 5.14.21-150400.24.158 fixes various security issues
The following security issues were fixed:
- CVE-2026-23191: ALSA: aloop: Fix racy access at PCM trigger (bsc#1258396).
- CVE-2026-23268: apparmor: fix unprivileged local user can do privileged policy management (bsc#1259859).
Список пакетов
SUSE Linux Enterprise Live Patching 15 SP4
Ссылки
- Link for SUSE-SU-2026:1578-1
- E-Mail link for SUSE-SU-2026:1578-1
- SUSE Security Ratings
- SUSE Bug 1258396
- SUSE Bug 1259859
- SUSE CVE CVE-2026-23191 page
- SUSE CVE CVE-2026-23268 page
Описание
In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Fix racy access at PCM trigger The PCM trigger callback of aloop driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are performed outside the cable lock, this may result in UAF when a program attempts to trigger frequently while opening/closing the tied stream, as spotted by fuzzers. For addressing the UAF, this patch changes two things: - It covers the most of code in loopback_check_format() with cable->lock spinlock, and add the proper NULL checks. This avoids already some racy accesses. - In addition, now we try to check the state of the capture PCM stream that may be stopped in this function, which was the major pain point leading to UAF.
Затронутые продукты
Ссылки
- CVE-2026-23191
- SUSE Bug 1258395
- SUSE Bug 1258396
Описание
In the Linux kernel, the following vulnerability has been resolved: apparmor: fix unprivileged local user can do privileged policy management An unprivileged local user can load, replace, and remove profiles by opening the apparmorfs interfaces, via a confused deputy attack, by passing the opened fd to a privileged process, and getting the privileged process to write to the interface. This does require a privileged target that can be manipulated to do the write for the unprivileged process, but once such access is achieved full policy management is possible and all the possible implications that implies: removing confinement, DoS of system or target applications by denying all execution, by-passing the unprivileged user namespace restriction, to exploiting kernel bugs for a local privilege escalation. The policy management interface can not have its permissions simply changed from 0666 to 0600 because non-root processes need to be able to load policy to different policy namespaces. Instead ensure the task writing the interface has privileges that are a subset of the task that opened the interface. This is already done via policy for confined processes, but unconfined can delegate access to the opened fd, by-passing the usual policy check.
Затронутые продукты
Ссылки
- CVE-2026-23268
- SUSE Bug 1258850
- SUSE Bug 1259859