Homepage

CVE-2025-38352 The advisory has been revoked - it doesn't affect any version of package kernel-rt-64k-debug-modules-extra  (opens in a new tab)

Threat Intelligence

Exploit Maturity
Attacked
EPSS
1.36% (72nd 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-ALMALINUX10-KERNELRT64KDEBUGMODULESEXTRA-12878667
  • published18 Sept 2025
  • disclosed11 Sept 2025
Report a new vulnerability Found a mistake?

Introduced: 11 Sep 2025

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

Amendment

The AlmaLinux security team deemed this advisory irrelevant for AlmaLinux:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-64k-debug-modules-extra package and not the kernel-rt-64k-debug-modules-extra package as distributed by AlmaLinux.

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.

References