Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 04218cd68d1502000823c8288f37b4f171dcdcae, 6ab3d4353bf75005eaa375677c9fed31148154d6, 83e0d8d22e7ee3151af1951595104887eebed6ab.

Low priority for now. Upgrade to Linux Linux 04218cd68d1502000823c8288f37b4f171dcdcae, 6ab3d4353bf75005eaa375677c9fed31148154d6, 83e0d8d22e7ee3151af1951595104887eebed6ab or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23049

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.19affected
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before f4c330b4499e7334ec6fce535574e09d55843d71affected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before bb309377eece5317207d71fd833f99cca4727fbdaffected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before 83e0d8d22e7ee3151af1951595104887eebed6abaffected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before bc0b17bdba3838e9e17e7e9adc968384ac99938baffected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before 04218cd68d1502000823c8288f37b4f171dcdcaeaffected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before f7940d3ec1dc6bf719eddc69d4b8e52cc2201896affected · git
    • 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 and later · before 6ab3d4353bf75005eaa375677c9fed31148154d6affected · git
    • before 4.19not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-71196Feb 4, 2026 · phy: stm32-usphyc: Fix off by one in probe()
    0Monitor
  • ← EarlierCVE-2025-71199Feb 4, 2026 · iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver
    0Monitor
  • Later →CVE-2026-23051Feb 4, 2026 · drm/amdgpu: fix drm panic null pointer when driver not support atomic
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux04218cd68d1502000823c8288f37b4f171dcdcaeVendor (CNA)
Linux Linux6ab3d4353bf75005eaa375677c9fed31148154d6Vendor (CNA)
Linux Linux83e0d8d22e7ee3151af1951595104887eebed6abVendor (CNA)
Linux Linuxbb309377eece5317207d71fd833f99cca4727fbdVendor (CNA)
Linux Linuxbc0b17bdba3838e9e17e7e9adc968384ac99938bVendor (CNA)
Linux Linuxf4c330b4499e7334ec6fce535574e09d55843d71Vendor (CNA)
Linux Linuxf7940d3ec1dc6bf719eddc69d4b8e52cc2201896Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records