PTP disruption via unchecked clock values
Published Nov 8, 2024 · Updated Aug 5, 2026
Improper input validation in the Linux kernel allows local users to disrupt PTP time services through an invalid clock setting. The pc_clock_settime() path passes negative tv_sec or out-of-range tv_nsec values to PTP driver settime64 callbacks without strict validation. Exploitation requires write access to a /dev/ptpN device and can poison the interface clock, interrupting hardware timestamps, synchronization, and time-aware transmission.
Summary
What happened
Improper input validation in the Linux kernel allows local users to disrupt PTP time services through an invalid clock setting. The pc_clock_settime() path passes negative tv_sec or out-of-range tv_nsec values to PTP driver settime64 callbacks without strict validation. Exploitation requires write access to a /dev/ptpN device and can poison the interface clock, interrupting hardware timestamps, synchronization, and time-aware transmission.
The record
- CVE
- CVE-2024-50195
- Published
- Nov 8, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-754
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <1ff7247101af723731ea42ed565d54fb8f341264
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <27abbde44b6e71ee3891de13e1a228aa7ce95bfe
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <29f085345cde24566efb751f39e5d367c381c584
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <673a1c5a2998acbd429d6286e6cad10f17f4f073
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <a3f169e398215e71361774d13bf91a0101283ac2
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <c8789fbe2bbf75845e45302cba6ffa44e1884d01
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <d8794ac20a299b647ba9958f6d657051fc51a540
- Affected versionversion=0606f422b453f76c31ab2b1bd52943ff06a2dcf2 <e0c966bd3e31911b57ef76cec4c5796ebd88e512
- Affected versionversion=2.6.39
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo