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

CVE-2026-72007

pmdomain: imx: Fix i.MX8MP VC8000E power up sequence

Description

In the Linux kernel, the following vulnerability has been resolved: pmdomain: imx: Fix i.MX8MP VC8000E power up sequence Per errata[1]: ERR050531: VPU_NOC power down handshake may hang during VC8000E/VPUMIX power up/down cycling. Description: VC8000E reset de-assertion edge and AXI clock may have a timing issue. Workaround: Set bit2 (vc8000e_clk_en) of BLK_CLK_EN_CSR to 0 to gate off both AXI clock and VC8000E clock sent to VC8000E and AXI clock sent to VPU_NOC m_v_2 interface during VC8000E power up(VC8000E reset is de-asserted by HW) Add a bool variable is_errata_err050531 in 'struct imx8m_blk_ctrl_domain_data' to represent whether the workaround is needed. If is_errata_err050531 is true, first clear the clk before powering up gpc, then enable the clk after powering up gpc. [1] https://www.nxp.com/webapp/Download?colCode=IMX8MP_1P33A

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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 88% of all CVEs (11 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 a1a5f15f7f6cb5c291f072af843305638c935be6 – < 9601551ceb039ab1c01cfa3aee153928a6d4f3c5
    • affected a1a5f15f7f6cb5c291f072af843305638c935be6 – < 87af3ebc112fb3f06753794390daf0f665f151b4
    • affected a1a5f15f7f6cb5c291f072af843305638c935be6 – < c498928f85651b56a4041ea165a22037eae69580
    • affected a1a5f15f7f6cb5c291f072af843305638c935be6 – < 4ff3960f3527189bc115a927ed3561c758f562f1
    • affected a1a5f15f7f6cb5c291f072af843305638c935be6 – < 4907f4c2d98b97e640191af5bcf2814ee1034b76
    • affected a1a5f15f7f6cb5c291f072af843305638c935be6 – < 25e252bcf1593b420b12a7231d9dd64b885a2ae2
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

6

Sources

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

Badge for a README or a ticket

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

Record last updated .