VulnerabilityPublished 6 May 2026Updated 11 May 2026

CVE-2026-43155: Linux kernel · mux: mmio: fix regmap leak on probe failure

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 11 Nov 2026, 22:47 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented in the Linux kernel by switching to a device-managed allocator for the mmio regmap. Users should update to the fixed Linux kernel version once available. No additional mitigation steps are indicated beyond applying the official kernel update.

Description

A resource leak vulnerability in the Linux kernel's mux mmio regmap handling was fixed. The issue involved the mmio regmap allocated during device probe not being freed on probe failure, potentially causing resource leaks. The fix involved switching to a device-managed allocator to ensure proper release of the regmap on probe failures and driver unbind events.

Impact

The vulnerability causes a resource leak (regmap) during device probe failures in the Linux kernel. While this does not directly lead to code execution or privilege escalation, it can result in wasted kernel memory resources and potentially degrade system stability if probe failures occur repeatedly without reboot or remediation.

Summary

CVE-2026-43155 addresses a resource management flaw in the Linux kernel's mux mmio regmap code. When a device probe fails, the mmio regmap allocated during the probe was not freed, leading to a regmap leak. The resolution was to adopt the device-managed allocator, which automatically releases the regmap on probe failure scenarios such as probe deferral and when the driver is unbound. This change prevents resource leaks that could degrade system stability over time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Nov 2026, 22:47 UTC

Technical details

References

Community reviews

Related threats