CVE-2025-21822

published 27 Feb 2025 · updated 11 May 2026

ptp: vmclock: Set driver data before its usage

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6dbd8b91a065d1d8001446a28e72cd140f9acef0 and Kernel f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce.

In the Linux kernel, the following vulnerability has been resolved: ptp: vmclock: Set driver data before its usage If vmclock_ptp_register() fails during probing, vmclock_remove() is called to clean up the ptp clock and misc device. It uses dev_get_drvdata() to access the vmclock state. However the driver data is not yet set at this point. Assign the driver data earlier.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.13, >=20503272422693d793b84f88bf23fe4e955d3a33 <6dbd8b91a065d1d8001446a28e72cd140f9acef0, >=20503272422693d793b84f88bf23fe4e955d3a33 <f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce6dbd8b91a065d1d8001446a28e72cd140f9acef0, f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-21822 severity on Zeptric[![CVE-2025-21822](https://zeptric.io/badge/cve/CVE-2025-21822.svg)](https://zeptric.io/cve/CVE-2025-21822)