CVE-2025-38352: Linux Kernel Time-of-Check Time-of-Use (TOCTOU) Race Condition Vulnerability

Published Jul 22, 2025
·
Updated

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.

Affected Software

20 affected componentsFixes available
Linux Linux kernel
Linux Kernel
Google Android
Linux Linux kernel>=2.6.36<5.4.295
Linux Linux kernel>=5.5<5.10.239
Linux Linux kernel>=5.11<5.15.186
Linux Linux kernel>=5.16<6.1.142
Linux Linux kernel>=6.2<6.6.94
Linux Linux kernel>=6.7<6.12.34
Linux Linux kernel>=6.13<6.15.3
Linux Linux kernel=6.16-rc1
Debian Debian Linux=11.0
IBM Cloud Pak System<=2.3.4.0
IBM Cloud Pak System<=2.3.4.1 2.3.4.1 ifix1
IBM Cloud Pak System<=2.3.5.0
IBM Cloud Pak System<=2.3.6.0
IBM OS Image for Red Hat Linux Systems<=4.0.4.0 4.0.5.0 4.0.6.0 4.0.7.0
IBM OS Image for Red Hat Linux Systems<=5.0.0.0 5.0.1.0
Microsoft azl3 kernel 6.6.92.2-2
Microsoft azl3 kernel 6.6.96.1-1

Event History

Jul 22, 2025
CVE Published
via MITRE·08:04 AM
Data Sourced
via MITRE·08:04 AM
Description
Data Sourced
via NVD·08:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·09:01 AM
DescriptionSeverityAffected Software
Aug 7, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Sep 2, 2025
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Sep 3, 2025
News Published
via BleepingComputer·02:14 PM
News Published
via BleepingComputer·02:15 PM
News Published
via The Register·09:51 PM
News Published
via The Register·09:55 PM
Sep 4, 2025
Known Exploited
via CISA·12:00 AM
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Jan 30, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-38352?

The severity of CVE-2025-38352 is categorized as medium due to its potential impact on system stability.

2

How do I fix CVE-2025-38352?

To fix CVE-2025-38352, update the Linux kernel to the latest stable version that includes the patch for this vulnerability.

3

What systems are affected by CVE-2025-38352?

CVE-2025-38352 affects various versions of the Linux kernel used in different distributions.

4

What are the potential consequences of CVE-2025-38352?

The potential consequences of CVE-2025-38352 include system instability and unexpected behavior during timer operations.

5

Is there an exploit available for CVE-2025-38352?

As of now, there is no known public exploit for CVE-2025-38352, but it is recommended to apply patches to mitigate risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203