Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < f4c330b4499e7334ec6fce535574e09d55843d71
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < bb309377eece5317207d71fd833f99cca4727fbd
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < 83e0d8d22e7ee3151af1951595104887eebed6ab
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < bc0b17bdba3838e9e17e7e9adc968384ac99938b
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < 04218cd68d1502000823c8288f37b4f171dcdcae
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < f7940d3ec1dc6bf719eddc69d4b8e52cc2201896
    • affected 97ceb1fb08b6a2f78aa44a7c229ca280964860c0 – < 6ab3d4353bf75005eaa375677c9fed31148154d6
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.67 – ≤ 6.12.*
    • unaffected 6.18.7 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23049 badge
[![CVE-2026-23049](https://cveledger.app/badge/CVE-2026-23049.svg)](https://cveledger.app/cve/CVE-2026-23049)

Record last updated .