CVE-2024-50195: Linux Kernel

Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days.

In the Linux kernel, the following vulnerability has been resolved: posix-clock: Fix missing timespec64 check in pc_clock_settime() As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct's tv_sec and tv_nsec range before calling ptp->info->settime64(). As the man manual of clock_settime() said, if tp.tv_sec is negative or tp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL, which include dynamic clocks which handles PTP clock, and the condition is consistent with timespec64_valid(). As Thomas suggested, timespec64_valid() only check the timespec is valid, but not ensure that the time is in a valid range, so check it ahead using timespec64_valid_strict() in pc_clock_settime() and return -EINVAL if not valid. There are some drivers that use tp->tv_sec and tp->tv_nsec directly to write registers without validity checks and assume that the higher layer has checked it, which is dangerous and will benefit from this, such as hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), and some drivers can remove the checks of itself.

Affected products

• Linux Linux Kernel: from 2.6.39, before 4.19.323 (fixed in 4.19.323); from 4.20, before 5.4.285 (fixed in 5.4.285); from 5.5, before 5.10.228 (fixed in 5.10.228); from 5.11, before 5.15.169 (fixed in 5.15.169); from 5.16, before 6.1.114 (fixed in 6.1.114); from 6.2, before 6.6.58 (fixed in 6.6.58); …

Published 2024-11-08. Last modified 2026-08-04.