Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-26969clk: qcom: gcc-ipq8074: fix terminating of frequency table arrays

Description

In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gcc-ipq8074: fix terminating of frequency table arrays The frequency table arrays are supposed to be terminated with an empty element. Add such entry to the end of the arrays where it is missing in order to avoid possible out-of-bound access when the table is traversed by functions like qcom_find_freq() or qcom_find_freq_floor(). Only compile tested.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26969, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < e117c6e2d1617520f5f7d7f6f6b395f01d8b5a27
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < 83fe1bbd9e259ad109827ccfbfc2488e0dea8e94
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < 851cc19bdb02556fb13629b3e4fef6f2bdb038fe
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < 9de184d4e557d550fb0b7b833b676bda4f269e4f
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < dd92b159c506804ac57adf3742d9728298bb1255
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < b6b31b4c67ea6bd9222e5b73b330554c57f2f90d
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < fc3ac2fcd0a7fad63eba1b359490a4b81720d0f9
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < be9e2752d823eca1d5af67014a1844a9176ff566
    • affected 9607f6224b3966652ce3f4e620c4694df190b64a – < 1040ef5ed95d6fd2628bad387d78a61633e09429
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 4.19.312 – ≤ 4.19.*
    • unaffected 5.4.274 – ≤ 5.4.*
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.154 – ≤ 5.15.*
    • unaffected 6.1.84 – ≤ 6.1.*
    • unaffected 6.6.24 – ≤ 6.6.*
    • unaffected 6.7.12 – ≤ 6.7.*
    • unaffected 6.8.3 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26969 badge
[![CVE-2024-26969](https://cveledger.app/badge/CVE-2024-26969.svg)](https://cveledger.app/cve/CVE-2024-26969)

Record last updated .