LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50210: posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()

In the Linux kernel, the following vulnerability has been resolved: posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime() If get_clock_desc() succeeds, it calls fget() for the clockid's fd, and get the clk->rwsem read lock, so the error path should release the lock to make the lock balance and fput the clockid's fd to make the refcount balance and release the fd related resource. However the below commit left the error path locked behind resulting in unbalanced locking. Check timespec64_valid_strict() before get_clock_desc() to fix it, because the "ts" is not changed after that. [pabeni@redhat.com: fixed commit message typo]

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-50210 is a Linux kernel availability issue in POSIX clock handling. A local authenticated user could trigger an error path that leaves locking and file-reference handling unbalanced, potentially causing denial of service. The public record rates it medium, with no evidence of active exploitation in the provided sources.

Executive priority

Treat this as a routine but time-bound kernel availability fix. It is not a remote takeover issue from the provided evidence, but shared Linux environments should patch promptly because local denial of service can still disrupt business services.

Technical view

The flaw is an unbalanced locking/refcount error in pc_clock_settime(). get_clock_desc() acquires resources, but one error path failed to release them. The fix validates the timespec before get_clock_desc(), avoiding the locked error path. CVSS 3.1 is 5.5: local attack, low complexity, low privileges, no confidentiality or integrity impact, high availability impact.

Likely exposure

Exposure is most relevant to Linux systems where local users, workloads, or tenants can call affected kernel clock paths. Risk depends on the actual running kernel and vendor backports, so distribution advisories and kernel package versions should drive scoping.

Exploitation context

The sources do not show public exploitation or CISA KEV listing. The CVSS vector requires local access with low privileges and no user interaction, so this is primarily a local denial-of-service concern rather than remote compromise.

Researcher notes

CWE-667 fits the resource locking failure. The provided data identifies the defect and stable fix commits, but does not provide affected version ranges beyond listed kernel release references. Validate using vendor advisories because downstream kernels may backport fixes without changing upstream version numbers.

Mitigation direction

  • Update to vendor-provided Linux kernel packages that include the referenced stable fixes.
  • Prioritize multi-user, shared hosting, CI, and tenant-dense Linux systems.
  • Check Debian LTS and appliance vendor advisories for backported kernel fixes.
  • Where patching is delayed, reduce unnecessary local shell or workload access.

Validation and detection

  • Inventory running kernel versions across servers, appliances, and container hosts.
  • Compare installed kernels against distribution advisories and stable kernel fix references.
  • Confirm reboot into the patched kernel after package installation.
  • Review vulnerability scanner findings for vendor backport awareness before closing.
Prepared
Confidence
high
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-667: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50210 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-50210Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux29f085345cde24566efb751f39e5d367c381c584, e0c966bd3e31911b57ef76cec4c5796ebd88e512, 673a1c5a2998acbd429d6286e6cad10f17f4f073, c8789fbe2bbf75845e45302cba6ffa44e1884d01, 27abbde44b6e71ee3891de13e1a228aa7ce95bfe, a3f169e398215e71361774d13bf91a0101283ac2, 1ff7247101af723731ea42ed565d54fb8f341264, d8794ac20a299b647ba9958f6d657051fc51a540unaffected
LinuxLinux5.10.228, 5.15.169, 6.1.114, 6.6.58, 6.11.5unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-667 · source CWE mapping

Improper Locking

Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.