CVE-2026-23132
Error Handling Flaws in Linux drm/bridge synopsys dw-dp Component
Publication date: 2026-02-14
Last updated on: 2026-03-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.18 (inc) to 6.18.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is in the Linux kernel's drm/bridge synopsys dw-dp driver, specifically in the dw_dp_bind() function's error handling.
- The function failed to return immediately after drm_bridge_attach() failed, causing continued execution despite an error.
- There was a resource leak because drm_dp_aux_register() is not managed automatically, so drm_dp_aux_unregister() must be called on all error paths after successful aux registration. This was missing in several error cases.
- An error handling bug existed where platform_get_irq() returns either an IRQ number or a negative error code, but the error path incorrectly returned ERR_PTR(ret) instead of ERR_PTR(dp->irq).
The fix involved using a goto label for cleanup to ensure consistent and correct error handling and resource cleanup.
How can this vulnerability impact me? :
This vulnerability can lead to improper error handling in the Linux kernel's display bridge driver, which may cause resource leaks and inconsistent system states.
Resource leaks can degrade system stability and performance over time.
Incorrect error returns may cause unexpected behavior in dependent components or drivers, potentially leading to system crashes or malfunctioning display hardware.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in the Linux kernel by correcting error handling in the dw_dp_bind() function of the drm/bridge synopsys dw-dp driver.
To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix.
The fix ensures proper error returns and resource cleanup to prevent resource leaks and incorrect error handling.