pmdomain: imx: Fix i.MX8MP VC8000E power up sequence
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 25e252bcf1593b420b12a7231d9dd64b885a2ae2, 4907f4c2d98b97e640191af5bcf2814ee1034b76, 4ff3960f3527189bc115a927ed3561c758f562f1.
Low priority for now. Upgrade to Linux Linux 25e252bcf1593b420b12a7231d9dd64b885a2ae2, 4907f4c2d98b97e640191af5bcf2814ee1034b76, 4ff3960f3527189bc115a927ed3561c758f562f1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.1affected
- a1a5f15f7f6cb5c291f072af843305638c935be6 and later · before 87af3ebc112fb3f06753794390daf0f665f151b4affected · git
- a1a5f15f7f6cb5c291f072af843305638c935be6 and later · before c498928f85651b56a4041ea165a22037eae69580affected · git
- a1a5f15f7f6cb5c291f072af843305638c935be6 and later · before 4ff3960f3527189bc115a927ed3561c758f562f1affected · git
- a1a5f15f7f6cb5c291f072af843305638c935be6 and later · before 4907f4c2d98b97e640191af5bcf2814ee1034b76affected · git
- a1a5f15f7f6cb5c291f072af843305638c935be6 and later · before 25e252bcf1593b420b12a7231d9dd64b885a2ae2affected · git
- before 6.1not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72004Aug 15, 2026 · wifi: mac80211: fix memory leak in ieee80211_register_hw()0Monitor
- ← EarlierCVE-2026-72006Aug 15, 2026 · net/mlx5: free mlx5_st_idx_data on final dealloc0Monitor
- Later →CVE-2026-72008Aug 15, 2026 · pmdomain: mediatek: Fix possible nullptr KP in HWV cleanup/on-check0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 25e252bcf1593b420b12a7231d9dd64b885a2ae2 | Vendor (CNA) |
| Linux Linux | 4907f4c2d98b97e640191af5bcf2814ee1034b76 | Vendor (CNA) |
| Linux Linux | 4ff3960f3527189bc115a927ed3561c758f562f1 | Vendor (CNA) |
| Linux Linux | 87af3ebc112fb3f06753794390daf0f665f151b4 | Vendor (CNA) |
| Linux Linux | c498928f85651b56a4041ea165a22037eae69580 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.