Security readout for executives and security teams
Plain-English summary
A missing end marker in Linux clock-frequency tables for Qualcomm IPQ9574 hardware can make the kernel read beyond the intended array. The supplied CVSS assessment indicates potential confidentiality, integrity, and availability impact, but exploitation requires local, low-privileged access. Exposure is likely concentrated in Linux systems using the affected IPQ9574 clock driver.
Executive priority
Treat this as a focused high-priority embedded-platform issue, not an organization-wide Linux emergency. Promptly identify IPQ9574 appliances, especially those permitting local untrusted activity, and obtain vendor-fixed kernels. Lower priority for systems that do not use the relevant Qualcomm platform. No active exploitation is established by the supplied evidence.
Technical view
Several gcc-ipq9574 frequency-table arrays lacked empty terminating elements. Kernel functions including qcom_find_freq() and qcom_find_freq_floor() could traverse beyond array bounds. The issue is scored CVSS 3.1 7.3 with local access, low complexity, low privileges, no user interaction, and unchanged scope. The correction adds missing terminators.
Likely exposure
Prioritize Linux-based routers, appliances, and embedded systems built on Qualcomm IPQ9574 and running an affected kernel. The supplied data lists 6.4, 6.6.24, 6.7.12, 6.8.3, and 6.9, but does not clearly express complete version ranges. Systems without this hardware or driver are unlikely to reach the vulnerable code.
Exploitation context
The CVSS vector describes local, low-privileged exploitation without user interaction; this is not presented as a remote network vulnerability. The supplied bundle says the CVE is not in KEV and provides no evidence of active exploitation or a public exploit. Real-world exploitability is uncertain because the correction was only compile tested.
Researcher notes
The root defect is unterminated frequency-table arrays causing possible out-of-bounds traversal. No CWE is supplied. The record provides four stable-kernel correction commits but unclear affected-range semantics and no runtime validation evidence. Assess reachability through the IPQ9574 clock paths and distinguish upstream version numbers from distribution kernels carrying backports.
Mitigation direction
- Obtain a kernel package containing the applicable upstream stable correction from the system or distribution vendor.
- Prioritize IPQ9574 appliances where untrusted users or processes can obtain local access.
- Restrict local access and reduce unnecessary low-privileged workloads until affected systems are updated.
- Check vendor advisories when version status cannot be determined from the supplied affected-version data.
Validation and detection
- Inventory kernel versions and identify systems built on Qualcomm IPQ9574 hardware.
- Confirm whether the gcc-ipq9574 clock driver is present and applicable on each system.
- Verify the vendor kernel includes the relevant stable correction, accounting for backported patches.
- After updating, confirm the running kernel changed and review logs for clock-driver or memory-access anomalies.
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.
CVE-2024-26968 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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
1 official scoreWe 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:L/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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/0204247cf3669b6021fb745c3b7f37ae392ab19cCVE reference, Linux
- https://git.kernel.org/stable/c/1723629fea8a4e75333196866e10d395463dca72CVE reference, Linux
- https://git.kernel.org/stable/c/604f2d7c46727c5e24fc7faddc980bc1cc0b1011CVE reference, Linux
- https://git.kernel.org/stable/c/bd2b6395671d823caa38d8e4d752de2448ae61e1CVE 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.