# What is CVE-2022-22706?

> CVE-2022-22706 is a high-severity flaw (CVSS 7.8) in Bifrost GPU Kernel Driver from Arm, published on 3 March 2022. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 1.1%. If you run an affected version, patch it first.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-22706

## At a glance

- **Verdict:** Fix this now. Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
- **Precursor Intelligence risk score:** 74 out of 100 (High); action: Emergency patch. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 7.8 out of 10)
- **Known to be exploited:** Yes, it is on the government list of flaws known to be exploited
- **Chance of use in the next 30 days:** 1.1% (latest exploit-likelihood forecast)
- **Published:** 3 March 2022
- **Record last updated:** 3 November 2025
- **Main product:** Bifrost GPU Kernel Driver from Arm
- **Affected products:** 3

## What is CVE-2022-22706? In plain terms

An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### The official description

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.

### What kind of flaw is it?

- CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer

### How an attack on it works

- Where an attacker can be: Already on the device
- How hard it is to pull off: Easy: no special conditions
- Login needed first: An ordinary user account
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`

## Is CVE-2022-22706 being exploited? Yes

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 1.1%.

Exploit likelihood over the last 7 days: 1.1%, 1.1%, 1.1%, 1.1%, 1.1%, 1.1%, 1.1%.

### Timeline

- 3 March 2022: Published
- 3 November 2025: Record last updated
- 19 November 2025: Exploit likelihood jumped
- 22 November 2025: Exploit likelihood fell

### How Precursor Intelligence ranks it

CVE-2022-22706 scores **74 out of 100 (High)**, with the action "Emergency patch".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2022-22706?

The published record lists 3 products. Versions are as published: "r0p0 to before r36p0" means from r0p0 up to, but not including, r36p0.

- [Bifrost GPU Kernel Driver](https://www.precursorintelligence.com/product/arm/bifrost_gpu_kernel_driver) by [Arm](https://www.precursorintelligence.com/vendors/arm) (Application): r0p0 to before r36p0
- [Midgard GPU Kernel Driver](https://www.precursorintelligence.com/product/arm/midgard_gpu_kernel_driver) by [Arm](https://www.precursorintelligence.com/vendors/arm) (Application): r26p0 to before r32p0
- [Valhall GPU Kernel Driver](https://www.precursorintelligence.com/product/arm/valhall_gpu_kernel_driver) by [Arm](https://www.precursorintelligence.com/vendors/arm) (Application): r19p0 to before r36p0

## How do I fix CVE-2022-22706?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Check it wasn’t used before you patched.** Because criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.

### References

- [developer.arm.com](https://developer.arm.com/support/arm-security-updates) (Vendor advisory)
- [developer.arm.com](https://developer.arm.com/support/arm-security-updates/mali-gpu-kernel-driver) (Vendor advisory)
- [cisa.gov](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22706) (Government resource)

## Questions

### What is CVE-2022-22706?

CVE-2022-22706 is a high-severity flaw in Bifrost GPU Kernel Driver from Arm, published on 3 March 2022. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2022-22706?

It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-22706 is 74 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.

### Is CVE-2022-22706 being exploited?

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 1.1%.

### Which versions does CVE-2022-22706 affect?

For Bifrost GPU Kernel Driver from Arm: r0p0 to before r36p0. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2022-22706?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.

## Does CVE-2022-22706 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact