Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

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.

Metrics

CVSS 3.x Severity and Vector Strings:

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

Weakness Enumeration

CWE-IDCWE NameSource
NVD-CWE-noinfoInsufficient Information to Classify Weakness[email protected]

Affected Products

ProductVersions
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

CPE

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:*

Remediation

  • No remediation found in references.
debian debian linux
11.0

CPE

  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

Remediation

  • No remediation found in references.

Change History

7 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2025-38305
NVD Published Date:
Jul 10, 2025
NVD Last Modified:
Nov 5, 2026
Source:
kernel.org
CVE-2025-38305 Details - Not Deferred