Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-38352

7.8 · HIGHActively Exploited

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 a…

Published Jul 22, 2025CWE-367EPSS 1.34%

Overview

CVE-2025-38352 is a high-severity vulnerability. It was published on July 22, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH). This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild.

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ffRefgit.kernel.org/stable/c/2f3daa04a9328220de46f0d5c919a6c0073a9f0bRefgit.kernel.org/stable/c/460188bc042a3f40f72d34b9f7fc6ee66b0b757bRefgit.kernel.org/stable/c/764a7a5dfda23f69919441f2eac2a83e7db6e5bbRefgit.kernel.org/stable/c/78a4b8e3795b31dae58762bc091bb0f4f74a2200Refgit.kernel.org/stable/c/c076635b3a42771ace7d276de8dc3bc76ee2ba1bRefgit.kernel.org/stable/c/c29d5318708e67ac13c1b6fc1007d179fb65b4d7Refgit.kernel.org/stable/c/f90fff1e152dedf52b932240ebbd670d83330ecaReflists.debian.org/debian-lts-announce/2025/10/msg00007.htmlReflists.debian.org/debian-lts-announce/2025/10/msg00008.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-38352?

CVE-2025-38352 is a high-severity vulnerability. It was published on July 22, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH). This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild.

How severe is CVE-2025-38352?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38352?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38352?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38352 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999