CVE-2025-38352

Linux

CVSS 7.4 HighKEV
  • CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Published: 2025-07-22T08:15:23.577
  • Vendors: Linux

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.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

  1. CVE-2025-38352 (CVSS 7.4)
  2. CVE-1999-0216 (no score)
  3. CVE-2000-0344 (no score)
  4. CVE-1999-0401 (no score)
  5. CVE-1999-0128 (no score)
  6. CVE-1999-1018 (no score)
  7. CVE-1999-0513 (no score)
  8. CVE-1999-0656 (no score)
  9. CVE-1999-0171 (no score)
  10. CVE-1999-0720 (no score)

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2025-38352

CVE-2025-38352 is a high severity vulnerability affecting Linux the affected product.

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 […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public
🚨 KEV Status: This vulnerability is actively exploited in the wild!

Vulnerability Timeline

Jul 22, 2025
Vulnerability Published

CVE details first published to NVD database

KEV
Added to Known Exploited Vulnerabilities

CISA confirmed active exploitation in the wild

Oct 28, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

Linux