posix-clock: Fix missing timespec64 check in pc_clock_settime()
Summary
| CVE | CVE-2024-50195 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2024-11-08 06:15:16 UTC |
| Updated | 2026-08-04 11:21:31 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-754 | CWE-754 CWE-754 Improper Check for Unusual or Exceptional Conditions
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Primary | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | ADP | DECLARED | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.1 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 5.5 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 7.1 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 29f085345cde24566efb751f39e5d367c381c584 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 e0c966bd3e31911b57ef76cec4c5796ebd88e512 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 673a1c5a2998acbd429d6286e6cad10f17f4f073 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 c8789fbe2bbf75845e45302cba6ffa44e1884d01 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 27abbde44b6e71ee3891de13e1a228aa7ce95bfe git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 a3f169e398215e71361774d13bf91a0101283ac2 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 1ff7247101af723731ea42ed565d54fb8f341264 git | Not specified |
| CNA | Linux | Linux | affected 0606f422b453f76c31ab2b1bd52943ff06a2dcf2 d8794ac20a299b647ba9958f6d657051fc51a540 git | Not specified |
| CNA | Linux | Linux | affected 2.6.39 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.39 semver | Not specified |
| CNA | Linux | Linux | unaffected 4.19.323 4.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.4.285 5.4.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.228 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.169 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.114 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.58 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.11.5 6.11.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| lists.debian.org/debian-lts-announce/2025/03/msg00002.html | af854a3a-2127-422b-91ae-364da2661108 | lists.debian.org | |
| git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| lists.debian.org/debian-lts-announce/2025/01/msg00001.html | af854a3a-2127-422b-91ae-364da2661108 | lists.debian.org | |
| git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.