# CVE-2026-23049: drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel

> Missing connector type in Linux kernel panel driver causes kernel warnings and prevents panel operation, leading to local 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:** 4 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-77307, BELL-CVE-2026-23049, DEBIAN-CVE-2026-23049, GHSA-gp84-h2r5-7wwf, ROOT-OS-UBUNTU-2204-CVE-2026-23049, ROOT-OS-UBUNTU-2404-CVE-2026-23049, UBUNTU-CVE-2026-23049

## What is CVE-2026-23049?

CVE-2026-23049 is a denial of service vulnerability in Linux, published on 4 Feb 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/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel

The connector type for the DataImage SCF0700C48GGU18 panel is missing and
devm_drm_panel_bridge_add() requires connector type to be set. This leads
to a warning and a backtrace in the kernel log and panel does not work:
"
WARNING: CPU: 3 PID: 38 at drivers/gpu/drm/bridge/panel.c:379 devm_drm_of_get_bridge+0xac/0xb8
"
The warning is triggered by a check for valid connector type in
devm_drm_panel_bridge_add(). If there is no valid connector type
set for a panel, the warning is printed and panel is not added.
Fill in the missing connector type to fix the warning and make
the panel operational once again.

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


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

Apply the vendor's patch.

## Is CVE-2026-23049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23049 is a denial of service vulnerability in Linux, published on 4 Feb 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-23049 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-23049/ (Markdown: https://insights.sbomify.com/CVE-2026-23049/index.md)
```

## Sources

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

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