CVE-2026-43072 Details
Description
In the Linux kernel, the following vulnerability has been resolved: drm/vc4: platform_get_irq_byname() returns an int platform_get_irq_byname() will return a negative value if an error happens, so it should be checked and not just passed directly into devm_request_threaded_irq() hoping all will be ok.
A vulnerability exists in the Linux kernel's VC4 Direct Rendering Manager (DRM) module related to improper handling of interrupt requests. The issue arises in the HDMI hotplug initialization function, where the platform_get_irq_byname() function is used to retrieve IRQ numbers for hotplug events. If this function encounters an error, it returns a negative value, which should be checked before proceeding. However, the current implementation directly passes the IRQ number to devm_request_threaded_irq() without verifying if the retrieval was successful. This oversight could lead to unhandled errors and potential instability.
Users can apply the latest patches from the Linux kernel stable tree, which include the necessary checks for IRQ retrieval errors before requesting threaded IRQs. These patches are available in the Linux Git repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15, < 6.6.136 >= 6.7, < 6.12.83 >= 6.13, < 6.18.24 >= 6.19, < 6.19.14 >= 7.0, < 7.0.1 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 1, 2026 | CVE Modified | kernel.org |
| May 29, 2026 | Initial Analysis | [email protected] |
| May 5, 2026 | New CVE Received | kernel.org |