LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43072: drm/vc4: platform_get_irq_byname() returns an int

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.

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-43072 is a Linux kernel issue in the drm/vc4 graphics driver. The code failed to handle an error return correctly when requesting an interrupt. Public sources do not provide a CVSS score, concrete security impact, or evidence of exploitation. Treat it as a kernel maintenance fix requiring exposure review, not an emergency without additional vendor guidance.

Executive priority

Medium-low unless your environment relies on affected Linux kernels with vc4 graphics support. There is no published severity or exploitation evidence in the supplied sources, but kernel defects should be remediated through normal patch cycles once vendor updates are available.

Technical view

In drm/vc4, platform_get_irq_byname() can return a negative error value. The vulnerable code passed that value into devm_request_threaded_irq() instead of checking it first. The CVE record says this has been resolved in the Linux kernel. The provided data lists affected Linux kernel versions and multiple stable kernel commits, but no CWE, CVSS, or exploitability details.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel builds with the drm/vc4 driver relevant to the platform. Systems not using this driver may have no practical exposure. Confirm against your distribution kernel package, enabled drivers, hardware profile, and vendor advisories.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The public description indicates an error-handling flaw, but does not describe attacker prerequisites, reachable attack surface, privilege requirements, or direct impact.

Researcher notes

The record lacks CVSS, CWE, and impact detail. Analysis should focus on code-path reachability, whether negative IRQ values can trigger security-relevant behavior, and which stable branches contain the fix. Do not infer remote or local exploitability from the current public record alone.

Mitigation direction

  • Check your Linux distribution or kernel vendor advisory for fixed packages.
  • Prioritize kernel updates for systems using the drm/vc4 driver.
  • Review the referenced stable commits if maintaining a custom kernel.
  • If updates are unavailable, ask the vendor for supported mitigation guidance.
  • Avoid assuming risk is eliminated solely because VC4 hardware is absent.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Identify systems with the drm/vc4 driver built, loaded, or packaged.
  • Compare kernel source or package changelog against referenced stable commits.
  • Confirm vendor packages include the CVE-2026-43072 fix.
  • Document systems not exposed due to driver or platform absence.
Prepared
Confidence
medium
Sources
9

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-43072 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
8Source 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
LinuxLinuxf4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2, f4790083c7c23b419f6a15170556950fd6a884a2unaffected
LinuxLinux5.15, 0, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1affected
Weakness

CWE details

No CWE listed

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