VulnerabilityPublished 27 Jul 2026Updated 9 Nov 2026

CVE-2026-64521: Linux kernel · pinctrl: meson: amlogic-a4: fix deadlock issue

Affects Linux kernelSource GCVE Database

Compare

Authoritative record:CVE-2026-64521· Medium

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 9 Nov 2026, 15:33 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1013.13~24.04.1, 7.0.0-1011.11~24.04.1 +12

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 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 9 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

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-28.28	Fixed in 7.0.0-28.28
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1009.9	Fixed in 7.0.0-1009.9
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1010.10	Fixed in 7.0.0-1010.10
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1009.9	Fixed in 7.0.0-1009.9
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.8	Fixed in 7.0.0-1008.8
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1003.4	Fixed in 7.0.0-1003.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and included in Linux kernel versions 7.0.0-28.28~24.04.1 and later. Users should update to these fixed versions or later to resolve the deadlock issue. No additional mitigation steps are required beyond applying the official patch.

Description

A deadlock vulnerability was identified and fixed in the Linux kernel's pinctrl subsystem for the Amlogic A4 platform. The issue occurs when accessing the pinconf-pins sysfs node, where a mutex is acquired twice leading to a deadlock. The fix replaces the problematic function call with a non-locking variant to prevent this condition.

Impact

The deadlock can cause the system or affected processes to hang when accessing the pinconf-pins sysfs node, potentially impacting system stability or availability. The severity is rated low, and there is no indication of privilege escalation or data compromise.

Summary

CVE-2026-64521 addresses a deadlock issue in the Linux kernel's pinctrl: meson: amlogic-a4 driver. The vulnerability arises because pinconf_pins_show() holds the pctldev->mutex and then calls pinctrl_find_gpio_range_from_pin(), which attempts to acquire the same mutex again, causing a deadlock. The resolution involves using pinctrl_find_gpio_range_from_pin_nolock() instead, which does not acquire the mutex, thereby preventing the deadlock.

References

Community reviews

Loading reviews…