Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2022-22706 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Arm Bifrost Gpu Kernel Driver. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 36% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-22706 is a vulnerability in the Arm Mali GPU Kernel Driver that permits a non-privileged user to gain write access to read-only memory pages. It affects Midgard GPU kernel drivers from r26p0 through r31p0, Bifrost drivers from r0p0 through r35p0, and Valhall drivers from r19p0 through r35p0. The flaw carries a CVSS 3.1 base score of 7.8 and is categorized under CWE-119.
A local attacker with a low-privileged account on an affected system can exploit the issue to corrupt memory protections, potentially leading to full confidentiality, integrity, and availability impacts without user interaction.
Arm has published security updates addressing the Mali GPU kernel driver on its developer portal, and administrators should apply the vendor-supplied patches for the listed GPU families. The vulnerability also appears in CISA’s catalog of known exploited vulnerabilities.
EPSS for the CVE rose sharply from a low baseline to a peak of 0.8356 on 2023-07-05 before receding to its current value of 0.0009, indicating a period of heightened post-disclosure exploitation interest that warrants renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-27849
Vulnerability Data
Arm Mali GPU Kernel Driver allows a non-privileged user to achieve write access to read-only memory pages. This affects Midgard r26p0 through r31p0, Bifrost r0p0 through r35p0, and Valhall r19p0 through r35p0.
- CWE(s)
- KEV Date Added
- 30 March 2023
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, testing including code scans and penetration tests, developer training) that reach buffer management and can stop many buffer overruns from reaching production, but leaves a bounded remainder (e.g. flaws in non-software components, incomplete enforcement of guidelines, or post-deployment changes)
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
A.8.27 mandates security-by-design principles (e.g. least privilege, fail securely, distrust external input, hardening) plus design reviews that can catch and stop buffer-boundary errors before they reach code, but this is only one minority slice of CWE-119's broad surface (language-specific flaws, unsafe library use, compiler/runtime mitigations, and post-deployment instances remain outside its direct scope).
Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.
Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-119, a class-level weakness. Rules are authored against its narrower children: CWE-823.