DEBIAN-CVE-2025-38352

Advisory lineage Upstream: 1 Downstream: 3
Upstream
CVE-2025-38352
Published: 22 Jul 2025, 08:15
Last modified:28 Apr 2026, 20:29

Vulnerability Summary

Overall Risk (default)
medium
30/100
CVSS Score
7.4 HIGH
3.1 (osv_debian)
EPSS Score
No data
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

22 Jul 2025, 08:15
Published
Vulnerability first disclosed
28 Apr 2026, 20:29
Last Modified
Vulnerability information updated

Description

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 Metrics

  • v3.1•HIGH•Score: 7.4CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected Systems

  • debian•linux

    < 5.10.244-1 | < 6.1.147-1 | < 6.12.35-1 | < 6.12.35-1

  • debian•linux-6.1

    < 6.1.153-1~deb11u1

References (1)