ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-38305

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

Published Jul 10, 2025 · catalog updated May 11, 2026 · Linux Linux

Check this week

CVE-2025-38305 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
None0.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
18.00%
Remediation
Version ranges on file
Affected products
vendor Linux Linux 73f37068d540eba5f93ba3a0019bf479d35ebd76 <5d217e7031a5c06d366580fc6ddbf43527b780d4

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 -------------------------------------------- sy

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Linux Linux 73f37068d540eba5f93ba3a0019bf479d35ebd76 <5d217e7031a5c06d366580fc6ddbf43527b780d473f37068d540eba5f93ba3a0019bf479d35ebd76 <5d217e7031a5c06d366580fc6ddbf43527b780d4

How to fix CVE-2025-38305

  • Recommended remediation

    Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-38305 is not in CISA KEV. FIRST estimates a 18.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.

Which versions are affected?

Compare what you have installed with Linux Linux 73f37068d540eba5f93ba3a0019bf479d35ebd76 <5d217e7031a5c06d366580fc6ddbf43527b780d4 73f37068d540eba5f93ba3a0019bf479d35ebd76 <5d217e7031a5c06d366580fc6ddbf43527b780d4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 18.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 10, 2025 · EUVD

    Detected

    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 tr

  2. May 11, 2026 · EUVD

    Updated

    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 tr

Sources

  • EUVDVulnerability recordEUVD-2025-20943

    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

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog May 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.