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-2026-90295cpufreq: imx6q: fix out-of-bounds write when probed more than once

Description

In the Linux kernel, the following vulnerability has been resolved: cpufreq: imx6q: fix out-of-bounds write when probed more than once imx6_soc_volt is allocated fresh on every probe, sized to the number of ARM OPPs: imx6_soc_volt = devm_kcalloc(cpu_dev, num, sizeof(*imx6_soc_volt), GFP_KERNEL); but it is filled through soc_opp_count, which has static storage and is never reset. A second bind after an unbind keeps indexing from where the first one stopped, and writes past the end of the new array. Unbinding and rebinding the driver on qemu's mcimx6ul-evk, under KASAN: BUG: KASAN: slab-out-of-bounds in imx6q_cpufreq_probe+0x3b0/0xa34 Write of size 4 at addr c5e90480 by task binder/73 imx6q_cpufreq_probe from platform_probe+0x88/0xe4 platform_probe from really_probe+0x108/0x384 bind_store from kernfs_fop_write_iter+0x1b4/0x28c The write lands one u32 past the end of the allocation. soc_opp_count is only read a few lines below the loop that fills it, so it never needed static storage. Make it a local.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 263a35331169390f7f9ccb51d74e668610199af4
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 49f2f9b1d0cc76cf221306fc707703205bd27073
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < c5135bc34ea37e9d19f758e61ac44415afb3891a
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 55864b26c22cbd4b2e0d36154a8c35931c2e133b
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < aaa66e60c0e21d19993a95bc3718dc29eb2d3192
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 55516986a3d81325c84f2d4ae9cd03116bc63599
    • affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .