{"id":"CVE-2024-50195","summary":"posix-clock: Fix missing timespec64 check in pc_clock_settime()","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nposix-clock: Fix missing timespec64 check in pc_clock_settime()\n\nAs Andrew pointed out, it will make sense that the PTP core\nchecked timespec64 struct's tv_sec and tv_nsec range before calling\nptp-\u003einfo-\u003esettime64().\n\nAs the man manual of clock_settime() said, if tp.tv_sec is negative or\ntp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL,\nwhich include dynamic clocks which handles PTP clock, and the condition is\nconsistent with timespec64_valid(). As Thomas suggested, timespec64_valid()\nonly check the timespec is valid, but not ensure that the time is\nin a valid range, so check it ahead using timespec64_valid_strict()\nin pc_clock_settime() and return -EINVAL if not valid.\n\nThere are some drivers that use tp-\u003etv_sec and tp-\u003etv_nsec directly to\nwrite registers without validity checks and assume that the higher layer\nhas checked it, which is dangerous and will benefit from this, such as\nhclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(),\nand some drivers can remove the checks of itself.","modified":"2026-03-20T12:39:38.189476Z","published":"2024-11-08T05:54:10.183Z","related":["ALSA-2025:20518","SUSE-SU-2024:4314-1","SUSE-SU-2024:4315-1","SUSE-SU-2024:4316-1","SUSE-SU-2024:4318-1","SUSE-SU-2024:4364-1","SUSE-SU-2024:4367-1","SUSE-SU-2024:4376-1","SUSE-SU-2024:4387-1","SUSE-SU-2025:0035-1","SUSE-SU-2025:0556-1","SUSE-SU-2025:0577-1","SUSE-SU-2025:0577-2","SUSE-SU-2025:20163-1","SUSE-SU-2025:20164-1","SUSE-SU-2025:20246-1","SUSE-SU-2025:20247-1","USN-7276-1","USN-7277-1","openSUSE-SU-2024:14500-1","openSUSE-SU-2025:14705-1"],"database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50195.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264"},{"type":"WEB","url":"https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe"},{"type":"WEB","url":"https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584"},{"type":"WEB","url":"https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073"},{"type":"WEB","url":"https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512"},{"type":"WEB","url":"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"},{"type":"WEB","url":"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50195.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50195"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"0606f422b453f76c31ab2b1bd52943ff06a2dcf2"},{"fixed":"29f085345cde24566efb751f39e5d367c381c584"},{"fixed":"e0c966bd3e31911b57ef76cec4c5796ebd88e512"},{"fixed":"673a1c5a2998acbd429d6286e6cad10f17f4f073"},{"fixed":"c8789fbe2bbf75845e45302cba6ffa44e1884d01"},{"fixed":"27abbde44b6e71ee3891de13e1a228aa7ce95bfe"},{"fixed":"a3f169e398215e71361774d13bf91a0101283ac2"},{"fixed":"1ff7247101af723731ea42ed565d54fb8f341264"},{"fixed":"d8794ac20a299b647ba9958f6d657051fc51a540"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50195.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}