LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23132: drm/bridge: synopsys: dw-dp: fix error paths of dw_dp_bind

In the Linux kernel, the following vulnerability has been resolved: drm/bridge: synopsys: dw-dp: fix error paths of dw_dp_bind Fix several issues in dw_dp_bind() error handling: 1. Missing return after drm_bridge_attach() failure - the function continued execution instead of returning an error. 2. Resource leak: drm_dp_aux_register() is not a devm function, so drm_dp_aux_unregister() must be called on all error paths after aux registration succeeds. This affects errors from: - drm_bridge_attach() - phy_init() - devm_add_action_or_reset() - platform_get_irq() - devm_request_threaded_irq() 3. Bug fix: platform_get_irq() returns the IRQ number or a negative error code, but the error path was returning ERR_PTR(ret) instead of ERR_PTR(dp->irq). Use a goto label for cleanup to ensure consistent error handling.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23132 is a Linux kernel bug in Synopsys DesignWare DisplayPort bridge initialization. When setup fails, the driver can continue incorrectly or leak resources. The public record does not provide a CVSS score, exploitation evidence, or a clear business-impact scenario.

Executive priority

Handle through normal kernel maintenance unless this driver is present on critical devices or vendor advisories raise severity. The missing CVSS and exploit evidence make emergency action unsupported by the provided sources, but affected fleet owners should still plan timely kernel updates.

Technical view

The issue is in dw_dp_bind() error handling. The fix adds consistent cleanup after auxiliary registration, returns properly after drm_bridge_attach() failure, and corrects the returned error for platform_get_irq(). The source describes a resolved Linux kernel vulnerability, but does not state privilege requirements or exploitability.

Likely exposure

Exposure appears limited to Linux systems running affected kernel code with the Synopsys dw-dp DisplayPort bridge driver present, especially relevant to embedded, SoC, or display-enabled platforms. The supplied data lists Linux 6.18/6.19-related affected versions but does not define all downstream distro status.

Exploitation context

No active exploitation is indicated. The CVE is not marked KEV, and the supplied sources do not describe public exploitation, proof of concept, or attacker path. Treat this as a kernel reliability and resource-handling issue unless vendor guidance states otherwise.

Researcher notes

The record is specific about flawed cleanup paths but sparse on security impact. Key unknowns are reachable failure conditions, attacker influence over initialization errors, and whether repeated failures could cause material denial of service. Avoid extrapolating beyond the kernel commit and CVE text.

Mitigation direction

  • Check Linux vendor or distribution advisories for fixed kernel packages.
  • Update to a kernel containing the referenced stable fixes when available.
  • For custom kernels, confirm the dw-dp error-path fix is backported.
  • Prioritize platforms using Synopsys DesignWare DisplayPort bridge hardware.
  • Track downstream distro status before declaring systems unaffected.

Validation and detection

  • Inventory kernel versions and downstream patch levels on relevant systems.
  • Confirm whether the Synopsys dw-dp driver is built or enabled.
  • Compare custom kernel trees against the referenced stable commits.
  • Review boot and display initialization logs for related driver failures.
  • Test display initialization after applying vendor kernel updates.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2026-23132 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux86eecc3a9c2e06462f6a273fcd24150b6da787de, 86eecc3a9c2e06462f6a273fcd24150b6da787deunaffected
LinuxLinux6.18, 0, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.