CVE-2024-50195

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.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*

History

29 Nov 2024, 20:26

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264 - () https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264 - Patch
References () https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe - () https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe - Patch
References () https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584 - () https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584 - Patch
References () https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073 - () https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073 - Patch
References () https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2 - () https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2 - Patch
References () https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01 - () https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01 - Patch
References () https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540 - () https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540 - Patch
References () https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512 - () https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512 - Patch
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CWE CWE-754
First Time Linux linux Kernel
Linux
CPE cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*

08 Nov 2024, 16:15

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: posix-clock: Arreglar la comprobación timespec64 faltante en pc_clock_settime() Como señaló Andrew, tendrá sentido que el núcleo PTP comprobara el rango tv_sec y tv_nsec de la estructura timespec64 antes de llamar a ptp->info->settime64(). Como decía el manual de manual de clock_settime(), si tp.tv_sec es negativo o tp.tv_nsec está fuera del rango [0..999,999,999], debería devolver EINVAL, que incluye relojes dinámicos que manejan el reloj PTP, y la condición es consistente con timespec64_valid(). Como sugirió Thomas, timespec64_valid() solo comprueba que el timespec sea válido, pero no garantiza que el tiempo esté en un rango válido, así que compruébelo con antelación usando timespec64_valid_strict() en pc_clock_settime() y devuelva -EINVAL si no es válido. Hay algunos controladores que usan tp->tv_sec y tp->tv_nsec directamente para escribir registros sin comprobaciones de validez y asumen que la capa superior lo ha comprobado, lo cual es peligroso y se beneficiará de esto, como hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), y algunos controladores pueden eliminar las comprobaciones de sí mismos.
References
  • () https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584 -
  • () https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512 -

08 Nov 2024, 06:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-11-08 06:15

Updated : 2024-11-29 20:26


NVD link : CVE-2024-50195

Mitre link : CVE-2024-50195

CVE.ORG link : CVE-2024-50195


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-754

Improper Check for Unusual or Exceptional Conditions