In the Linux kernel, the following vulnerability has been resolved:
pinctrl: mediatek: fix global-out-of-bounds issue
When eint virtual eint number is greater than gpio number,
it maybe produce 'desc[eint_n]' size globle-out-of-bounds issue.
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel bug in MediaTek pin control handling. Under certain numbering conditions, the kernel may read or write outside a global array. The source bundle does not provide impact details, CVSS, or known exploitation, so urgency depends on whether affected MediaTek-based Linux systems exist in your fleet.
Executive priority
Do not treat this as an internet-wide emergency from the provided evidence. Assign platform owners to confirm MediaTek Linux exposure and patch through normal kernel maintenance, escalating if affected devices are safety-critical, customer-facing, or hard to update.
Technical view
The flaw is described as a global out-of-bounds issue in the MediaTek pinctrl EINT path when a virtual EINT number exceeds the GPIO number and indexes desc[eint_n]. The record lists Linux kernel affected entries and four stable kernel commits as references. No CWE, CVSS, exploitability, or detailed attack prerequisites are provided.
Likely exposure
Exposure appears most relevant to Linux systems using the MediaTek pinctrl/EINT kernel code in the affected kernel versions listed by the CVE record. The bundle does not identify distributions, device models, configurations, or whether remote access is involved.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. They also do not describe a public exploit, attack path, privileges required, or user interaction requirements. Treat exploitation context as incomplete.
Researcher notes
The record is sparse: no CVSS, CWE, affected CPEs, exploit status, or attack prerequisites. Analysis should focus on code reachability in MediaTek pinctrl/EINT configurations and whether vendor kernels include one of the referenced stable commits.
Mitigation direction
Identify Linux assets using MediaTek kernel pinctrl or EINT support.
Update affected kernels to vendor releases containing the referenced stable fixes.
For self-maintained kernels, evaluate backporting the referenced upstream stable commits.
Check distribution or device vendor advisories before applying kernel changes.
Prioritize embedded, mobile, or appliance Linux systems using MediaTek SoCs.
Validation and detection
Inventory running kernel versions across MediaTek-based Linux systems.
Confirm whether the MediaTek pinctrl/EINT driver code is present or enabled.
Map kernel builds against the CVE record's affected versions and fix commits.
Review vendor kernel changelogs for the referenced stable commit identifiers.
After updating, confirm systems boot and hardware interrupt functions behave normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CVE-2021-47083 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.