CVE-2024-50195 is an input-validation vulnerability in the Linux kernel's pc_clock_settime() function. The function fails to validate the timespec64 timestamp before passing it to Precision Time Protocol (PTP) clock-setting operations through ptp->info->settime64(). Invalid inputs include negative seconds, nanoseconds outside 0–999,999,999, and timestamps outside the permitted time range. Some PTP drivers, including hclge_ptp_settime(), igb_ptp_settime_i210(), and _rcar_gen4_ptp_settime(), use these fields directly to program hardware registers, relying on validation by higher layers. The fix adds timespec64_valid_strict() validation and rejects invalid timestamps with -EINVAL.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel POSIX clock vulnerability caused by missing strict validation of time values in pc_clock_settime() before passing them to PTP drivers. The fix validates values using timespec64_valid_strict() and rejects invalid input with -EINVAL. The advisory assigns a CVSS v3 score of 5.5, indicating a local, low-privilege vulnerability with high availability impact.
Linux kernel POSIX clock timespec validation flaw.
Linux kernel POSIX-clock time structure validation flaw.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.