Skip to main content
VulnerabilityPublished Updated

CVE-2026-43242: Linux kernel · Memory Leak

Source GCVE Database

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 27 Oct 2026, 00:57 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

AI-suggested

A fix is available that switches the driver to use the device-managed allocator to automatically free the regmap on probe failure and driver unbind. Users should apply the updated Linux kernel version containing this fix once released. No additional mitigation is required beyond applying the official patch.

Description

A memory leak vulnerability in the Linux kernel's soc: ti: k3-socinfo driver was fixed. The issue involved the mmio regmap allocated during probe not being freed on probe failure, leading to resource leakage. The fix involved switching to a device-managed allocator to ensure proper release of the regmap on probe failures and driver unbind.

References

Community reviews

Loading reviews…