CVE-2025-38352 remediation guide
Linux Linux, linux kernel, debian 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 fi...
Identify the affected asset
Confirm whether Linux Linux, linux kernel, debian linux is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 78a4b8e3795b31dae58762bc091bb0f4f74a2200, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < c076635b3a42771ace7d276de8dc3bc76ee2ba1b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 2f3daa04a9328220de46f0d5c919a6c0073a9f0b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 764a7a5dfda23f69919441f2eac2a83e7db6e5bb, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < c29d5318708e67ac13c1b6fc1007d179fb65b4d7, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < 460188bc042a3f40f72d34b9f7fc6ee66b0b757b, >= 0bdd2ed4138ec04e09b4f8165981efc99e439f55 < f90fff1e152dedf52b932240ebbd670d83330eca, >= 2.6.36, >= 2.6.36 < 5.4.295, >= 5.5 < 5.10.239, >= 5.11 < 5.15.186, >= 5.16 < 6.1.142, >= 6.2 < 6.6.94, >= 6.7 < 6.12.34, >= 6.13 < 6.15.3, 6.16, 11.0. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.