# CVE-2022-50722: media: ipu3-imgu: Fix NULL pointer dereference in active selection access

> A NULL pointer dereference in the Linux kernel IMGU driver allows local attackers to cause a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50722, GHSA-vpqj-28g2-5g9m, UBUNTU-CVE-2022-50722

## What is CVE-2022-50722?

CVE-2022-50722 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

media: ipu3-imgu: Fix NULL pointer dereference in active selection access

What the IMGU driver did was that it first acquired the pointers to active
and try V4L2 subdev state, and only then figured out which one to use.

The problem with that approach and a later patch (see Fixes: tag) is that
as sd_state argument to v4l2_subdev_get_try_crop() et al is NULL, there is
now an attempt to dereference that.

Fix this.

Also rewrap lines a little.

## Which versions are affected by CVE-2022-50722?


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

Apply the vendor's patch.

## Is CVE-2022-50722 being exploited?

There is no known exploitation of CVE-2022-50722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50722 and fix it if it is affected.

What it is: CVE-2022-50722 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50722 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50722/ (Markdown: https://insights.sbomify.com/CVE-2022-50722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50722
- OSV: https://osv.dev/vulnerability/CVE-2022-50722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50722/
Summaries are generated and may contain mistakes; the official description above is the record.