# CVE-2026-90297: drm/sun4i: crtc: Propagate layer initialization error

> A null pointer dereference in the sun4i DRM driver causes a kernel oops when layer initialization fails, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102332, BELL-CVE-2026-90297, DEBIAN-CVE-2026-90297, GHSA-m975-xmq3-6qch, UBUNTU-CVE-2026-90297

## What is CVE-2026-90297?

CVE-2026-90297 is a vulnerability in Linux, published on 17 Sep 2026. 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:

drm/sun4i: crtc: Propagate layer initialization error

sun4i_crtc_init() returns plain NULL when layer initialization fails,
while all its other error paths return an error pointer. The only
caller, sun4i_tcon_bind(), checks the result with IS_ERR() and happily
continues with tcon->crtc set to NULL. sun4i_rgb_init() and
sun4i_lvds_init() then dereference it in drm_crtc_mask(), which
oopses.

Return the error pointer instead.

## Which versions are affected by CVE-2026-90297?


## How do I fix CVE-2026-90297?

Apply the vendor's patch.

## Is CVE-2026-90297 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90297 and fix it if it is affected.

What it is: CVE-2026-90297 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-90297 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-2026-90297/ (Markdown: https://insights.sbomify.com/CVE-2026-90297/index.md)
```

## Sources

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

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