Security readout for executives and security teams
Plain-English summary
CVE-2022-50236 is a Linux kernel issue in the MediaTek IOMMU driver. After a kexec-style reboot, an interrupt handler may run before required setup is complete, causing an invalid memory access and kernel crash. This appears most relevant to Linux systems using affected MediaTek hardware paths.
Executive priority
Treat as targeted remediation, not an emergency. Prioritize affected MediaTek-based Linux devices where unexpected reboot crashes could disrupt operations. Broad enterprise exposure is likely limited unless such hardware and kexec workflows are present.
Technical view
The bug is in iommu/mediatek. The IRQ handler mtk_iommu_isr can trigger before the IOMMU domain is initialized after kexec, leading to report_iommu_fault reading invalid memory. Kernel stable commits are referenced as fixes. The CVE record provides no CVSS score, CWE, or detailed exploitability assessment.
Likely exposure
Exposure appears limited to Linux kernels using the MediaTek IOMMU driver and kexec-related reboot flows. General Linux servers without MediaTek IOMMU hardware are unlikely to be affected based on the provided sources.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. The documented impact is a crash from invalid kernel memory access during a specific initialization timing condition after kexec.
Researcher notes
The source data lacks CVSS, CWE, and exploitability details. The affected-version list is sparse and should be reconciled with distribution backports. Analysis should focus on MediaTek IOMMU initialization ordering around kexec and the referenced stable kernel commits.
Mitigation direction
- Identify Linux systems using MediaTek IOMMU support.
- Review kernel vendor advisories for CVE-2022-50236 applicability.
- Update to a kernel containing the referenced stable fixes.
- If patching is delayed, assess whether kexec use can be reduced operationally.
Validation and detection
- Check whether deployed kernels include the referenced stable commits.
- Confirm whether MediaTek IOMMU driver support is enabled or in use.
- Review crash logs for mtk_iommu_isr or report_iommu_fault traces.
- Track distribution-specific CVE status and backport notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-50236 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f13acee780cedb3e06a6dadf64d9104cccd2b9fcCVE reference, Linux
- https://git.kernel.org/stable/c/85cc8a187f2de7a91e2cea522e9406fa12999269CVE reference, Linux
- https://git.kernel.org/stable/c/00ef8885a945c37551547d8ac8361cacd20c4e42CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.