Security readout for executives and security teams
Plain-English summary
A Linux kernel clock driver for Loongson2 systems can misstate an allocated array’s size. A subsequent out-of-bounds write could corrupt kernel memory, potentially causing system compromise or disruption. The risk is significant where the affected driver and hardware are present, but the supplied sources do not establish widespread exposure or exploitation.
Executive priority
Treat this as a high-priority, targeted kernel update for exposed Loongson2 systems, especially multi-user or workload-hosting environments. It is not evidence of an internet-wide emergency because exploitation requires local access and no active exploitation is documented. Quickly determine whether relevant hardware and driver code exist before escalating broadly.
Technical view
The loongson2 clock provider allocated its flexible hws array for clks_num elements but set the counted_by counter, clk_data.num, higher than that allocation. This could prevent compiler instrumentation from detecting access at hws[clks_num], allowing runtime memory corruption. The upstream correction sets num to clks_num. CVSS 3.1 is 7.8 with local, low-privilege access required.
Likely exposure
Exposure is likely limited to affected Linux kernels using the Loongson2 clock driver, principally relevant to corresponding Loongson2 hardware. The supplied affected-version data references 6.10 and later release points through 6.13, but its flattened version representation is ambiguous. Confirm exact affected ranges and downstream backports with the system’s kernel vendor.
Exploitation context
The supplied CVSS vector requires local access and low privileges, with no user interaction. Successful exploitation could affect confidentiality, integrity, and availability through kernel memory corruption. CISA KEV status is false, and no supplied source reports active exploitation or a public exploit. Practical reachability and reliability are not established by this bundle.
Researcher notes
The defect concerns counted_by metadata consistency and a potential out-of-bounds access in clk-loongson2. The sources describe possible runtime memory corruption but do not demonstrate a reachable trigger, exploitation primitive, proof of concept, or observed attacks. Exact affected ranges should be resolved from the CVE record and downstream vendor advisories because the supplied normalized version list is unclear.
Mitigation direction
- Upgrade to a vendor-supported kernel containing the cited upstream fix or an equivalent backport.
- Prioritize Loongson2 systems where untrusted users or local workloads can execute code.
- Consult distribution or appliance vendor guidance for exact fixed versions and reboot requirements.
- Restrict unnecessary local access until affected systems are patched.
Validation and detection
- Inventory kernel versions, hardware architecture, and whether the Loongson2 clock driver is present.
- Compare deployed kernel source or vendor changelogs with the cited stable fixes.
- Confirm the corrected code sets clk_data.num to clks_num.
- After updating, verify the fixed kernel is running and clock-dependent services operate normally.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-120: 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 lookupCVE-2024-53192 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/b96fc194984d0c82de1ca2b4166b35b1298b216cCVE reference, Linux
- https://git.kernel.org/stable/c/1bf8877150128c3abd9d233886a05f6966fbf0c7CVE reference, Linux
- https://git.kernel.org/stable/c/02fb4f0084331ef72c28d0c70fcb15d1bea369ecCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.