CVE-2025-38352 Affecting kernel-livepatch-6_12_0-160000_5-default package, versions <7-160000.4.3


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

Exploit Maturity
Attacked
EPSS
1.28% (68th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES1600-KERNELLIVEPATCH61201600005DEFAULT-15439822
  • published7 Mar 2026
  • disclosed4 Mar 2026

Introduced: 4 Mar 2026

CVE-2025-38352  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 kernel-livepatch-6_12_0-160000_5-default to version 7-160000.4.3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6_12_0-160000_5-default package and not the kernel-livepatch-6_12_0-160000_5-default package as distributed by SLES. See How to fix? for SLES:16.0.0 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()

If an exiting non-autoreaping task has already passed exit_notify() and calls handle_posix_cpu_timers() from IRQ, it can be reaped by its parent or debugger right after unlock_task_sighand().

If a concurrent posix_cpu_timer_del() runs at that moment, it won't be able to detect timer->it.cpu.firing != 0: cpu_timer_task_rcu() and/or lock_task_sighand() will fail.

Add the tsk->exit_state check into run_posix_cpu_timers() to fix this.

This fix is not needed if CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y, because exit_task_work() is called before exit_notify(). But the check still makes sense, task_work_add(&tsk->posix_cputimers_work.work) will fail anyway in this case.

CVSS Base Scores

version 3.1