Skip to main content
VulnerabilityPublished Updated

CVE-2026-23116: Linux kernel · pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd675de6bddf7e9bdf42ae3929d4c27ba6d1ef76 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fd675de6bddf7e9bdf42ae3929d4c27ba6d1ef76, cad7003d951e8899db58ee2fef211586af726f09, 8859e336d233e61a4c40d40dc6a9f21e8b9b719c +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 608d7c325e855cb4a853afef3cd9f0df594bd12d, < fd675de6bddf7e9bdf42ae3929d4c27ba6d1ef76
Fixed in
  • fd675de6bddf7e9bdf42ae3929d4c27ba6d1ef76
LinuxLinuxAffected
  • ≥ 608d7c325e855cb4a853afef3cd9f0df594bd12d, < cad7003d951e8899db58ee2fef211586af726f09
Fixed in
  • cad7003d951e8899db58ee2fef211586af726f09
LinuxLinuxAffected
  • ≥ 608d7c325e855cb4a853afef3cd9f0df594bd12d, < 8859e336d233e61a4c40d40dc6a9f21e8b9b719c
Fixed in
  • 8859e336d233e61a4c40d40dc6a9f21e8b9b719c
LinuxLinuxAffected
  • ≥ 608d7c325e855cb4a853afef3cd9f0df594bd12d, < 5c56a6f4b5a4f87c094c92a30fa17e28e37ec2ab
Fixed in
  • 5c56a6f4b5a4f87c094c92a30fa17e28e37ec2ab
LinuxLinuxAffected
  • ≥ 608d7c325e855cb4a853afef3cd9f0df594bd12d, < 3de49966499634454fd59e0e6fecd50baab7febd
Fixed in
  • 3de49966499634454fd59e0e6fecd50baab7febd
LinuxLinuxAffected
  • =5.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu For i.MX8MQ platform, the ADB in the VPUMIX domain has no separate reset and clock enable bits, but is ungated and reset together with the VPUs. So we can't reset G1 or G2 separately, it may led to the system hang. Remove rst_mask and clk_mask of imx8mq_vpu_blk_ctl_domain_data. Let imx8mq_vpu_power_notifier() do really vpu reset.

References

Community reviews

Loading reviews…