CVE-2022-50826: ipu3-imgu: Fix NULL pointer dereference in imgu_subdev_set_selection()
In the Linux kernel, the following vulnerability has been resolved:
ipu3-imgu: Fix NULL pointer dereference in imgu_subdev_set_selection()
Calling v4l2_subdev_get_try_crop() and v4l2_subdev_get_try_compose()
with a subdev state of NULL leads to a NULL pointer dereference. This
can currently happen in imgu_subdev_set_selection() when the state
passed in is NULL, as this method first gets pointers to both the "try"
and "active" states and only then decides which to use.
The same issue has been addressed for imgu_subdev_get_selection() with
commit 30d03a0de650 ("ipu3-imgu: Fix NULL pointer dereference in active
selection access"). However the issue still persists in
imgu_subdev_set_selection().
Therefore, apply a similar fix as done in the aforementioned commit to
imgu_subdev_set_selection(). To keep things a bit cleaner, introduce
helper functions for "crop" and "compose" access and use them in both
imgu_subdev_set_selection() and imgu_subdev_get_selection().
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel NULL pointer dereference in the ipu3-imgu media driver. Affected systems could crash or behave unexpectedly when specific selection handling reaches this bug. The source bundle does not provide CVSS, CWE, attack requirements, or confirmed business impact.
Executive priority
Track and patch through normal kernel maintenance unless your fleet depends on ipu3-imgu media functionality. Escalate if vendor advisories later assign meaningful severity or identify practical exploitation paths.
Technical view
imgu_subdev_set_selection() could call v4l2_subdev_get_try_crop() and v4l2_subdev_get_try_compose() with a NULL subdev state, causing a NULL pointer dereference. The fix mirrors prior get_selection handling by using helper functions for crop and compose state access.
Likely exposure
Exposure appears limited to Linux kernels using the ipu3-imgu driver and the affected V4L2 subdevice selection path. The source lists Linux as affected across versions including 5.14, 5.15.87, 6.0.18, 6.1.4, and 6.2, but does not describe distribution-specific packages.
Exploitation context
The source bundle does not indicate active exploitation, and KEV is false. It also does not provide exploitability details, privilege requirements, or remote attack evidence. Treat this as a kernel stability risk until vendor advisories clarify severity.
Researcher notes
Evidence is limited to the CVE description and Linux stable commit references. The flaw is a NULL dereference in set_selection state handling, related to an earlier get_selection fix. No CVSS, CWE, proof of exploitation, or precise distro remediation data is included.
Mitigation direction
Apply the relevant Linux stable kernel update containing the referenced fixes.
Check your Linux distribution advisory for backported kernel package status.
Prioritize systems where ipu3-imgu support is enabled or camera/media workloads are present.
If patching is delayed, review vendor guidance for safe driver exposure reduction.
Validation and detection
Inventory kernel versions and compare them with vendor fixed package guidance.
Confirm whether the ipu3-imgu driver is built, loaded, or required.
Review kernel changelogs for the referenced stable commits.
Run normal regression testing for camera and media workloads after updating.
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-2022-50826 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
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.
Dec 30, 2025, 12:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.