CVE-2025-38305 Details
Description
In the Linux kernel, the following vulnerability has been resolved: ptp: remove ptp->n_vclocks check logic in ptp_vclock_in_use() There is no disagreement that we should check both ptp->is_virtual_clock and ptp->n_vclocks to check if the ptp virtual clock is in use. However, when we acquire ptp->n_vclocks_mux to read ptp->n_vclocks in ptp_vclock_in_use(), we observe a recursive lock in the call trace starting from n_vclocks_store(). ============================================ WARNING: possible recursive locking detected 6.15.0-rc6 #1 Not tainted -------------------------------------------- syz.0.1540/13807 is trying to acquire lock: ffff888035a24868 (&ptp->n_vclocks_mux){+.+.}-{4:4}, at: ptp_vclock_in_use drivers/ptp/ptp_private.h:103 [inline] ffff888035a24868 (&ptp->n_vclocks_mux){+.+.}-{4:4}, at: ptp_clock_unregister+0x21/0x250 drivers/ptp/ptp_clock.c:415 but task is already holding lock: ffff888030704868 (&ptp->n_vclocks_mux){+.+.}-{4:4}, at: n_vclocks_store+0xf1/0x6d0 drivers/ptp/ptp_sysfs.c:215 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&ptp->n_vclocks_mux); lock(&ptp->n_vclocks_mux); *** DEADLOCK *** .... ============================================ The best way to solve this is to remove the logic that checks ptp->n_vclocks in ptp_vclock_in_use(). The reason why this is appropriate is that any path that uses ptp->n_vclocks must unconditionally check if ptp->n_vclocks is greater than 0 before unregistering vclocks, and all functions are already written this way. And in the function that uses ptp->n_vclocks, we already get ptp->n_vclocks_mux before unregistering vclocks. Therefore, we need to remove the redundant check for ptp->n_vclocks in ptp_vclock_in_use() to prevent recursive locking.
A vulnerability in the Linux kernel's Precision Time Protocol (PTP) implementation has been identified, related to improper locking mechanisms that can lead to deadlocks. The issue arises in the virtual clock management, where the function 'ptp_vclock_in_use()' incorrectly checks the number of virtual clocks in use, creating a potential for recursive locking. This vulnerability affects Linux kernel versions 6.15.0-rc6 and prior.
The recommended remediation is to remove the redundant check for 'ptp->n_vclocks' in the 'ptp_vclock_in_use()' function. This adjustment prevents the recursive locking issue by eliminating the unnecessary verification that could lead to a deadlock.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/259119595227fd20f6aa29d85abe086b6fdd9eb1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5d217e7031a5c06d366580fc6ddbf43527b780d4 | kernel.org | Patch |
| https://git.kernel.org/stable/c/87f7ce260a3c838b49e1dc1ceedf1006795157a2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b1b73c452331451020be3bf4b014901015ae6663 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b93e6fef4eda48e17d9c642b9abad98a066fd4a3 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ef8fc007c28a30a4c0d90bf755e0f343d99bb392 | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.14.1, < 5.15.186 >= 5.16, < 6.1.142 >= 6.2, < 6.6.94 >= 6.7, < 6.12.34 >= 6.13, < 6.15.3 5.14 - 5.14 rc2 5.14 rc3 5.14 rc4 5.14 rc5 5.14 rc6 5.14 rc7 6.16 rc1 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CVE |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 19, 2025 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| Jul 10, 2025 | New CVE Received | kernel.org |