CVE-2024-50195

MEDIUM EPSS 14.1%
Published Nov 8, 20241y ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Nov 8, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

Description

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
14.1% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-754

Affected Products 10

VendorProductVersionRange
linuxlinux_kernel*≥2.6.39  –  <4.19.323
linuxlinux_kernel*≥4.20  –  <5.4.285
linuxlinux_kernel*≥5.5  –  <5.10.228
linuxlinux_kernel*≥5.11  –  <5.15.169
linuxlinux_kernel*≥5.16  –  <6.1.114
linuxlinux_kernel*≥6.2  –  <6.6.58
linuxlinux_kernel*≥6.7  –  <6.11.5
linuxlinux_kernel6.12any
linuxlinux_kernel6.12any
linuxlinux_kernel6.12any

References 10

  • git.kernel.org https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512
    Patch