CVE-2026-74519

pinctrl: devicetree: don't free uninitialized dev_name on error path

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: don't free uninitialized dev_name on error path dt_remember_or_free_map() duplicates dev_name for each map entry. If kstrdup_const() fails, dt_free_map() frees dev_name in all num_maps entries, including entries that have not been initialized. Some pinctrl drivers, including pinctrl-imx, allocate the map with kmalloc() and leave dev_name for the core to initialize. The untouched entries therefore contain uninitialized data which is passed to kfree_const(). Reproduced on qemu's mcimx6ul-evk (pinctrl-imx) with failslab injection while binding the pinctrl-consuming device, under KASAN: BUG: KASAN: double-free in dt_free_map+0x34/0xa4 Free of addr c425a900 by task init/1 kfree from dt_free_map+0x34/0xa4 dt_free_map from dt_remember_or_free_map+0x184/0x198 dt_remember_or_free_map from pinctrl_dt_to_map+0x33c/0x4c8 pinctrl_dt_to_map from create_pinctrl+0x9c/0x5c0 Initialize all dev_name fields to NULL before duplicating the device name, making the full-map cleanup safe after a partial failure.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

03f69244302d7954f42f528ea2d45903ebbf59f33f69244302d7954f42f528ea2d45903ebbf59f34.14.1614.19.924.4.2444.9.2445.4.75.5679c4f27b8958b65bb51d1c3dfdbf3befe4a33a377440c3a37203e3f4667d06e37f76ef3968d2d8cbe4c60b563edee3712d392aaeb0943a768df7023f739a699db7d5a5cf39ca3ce2c84e4fe4a8f4c5df88ac1330779c5bfdd79f7d7f7d4d3343c782f92
Vendor states this is fixed in 015b5bcbcb622b32317642be91a7f79aa5413649 (fixed)
Vendor states this is fixed in 1586423da2739a80871ef6240016fcb9c7339bfb (fixed)
Vendor states this is fixed in 321fe3584a8298386938130d138191aa35040b75 (fixed)
Vendor states this is fixed in 929f6396baade89999ec8a1281232c101cbc727d (fixed)
Vendor states this is fixed in 9d00a5ac7cd3d32ae61140f4b8a62f136de84e7d (fixed)
Vendor states this is fixed in ad0ad3c228b6f76fde10f32047e0ec5fbc109dc8 (fixed)
Vendor states this is fixed in dec5f0a8080502908dec5e35597c7ae07d533a3b (fixed)
Vendor states this is fixed in e3cfb22bad363bebcfd55d909e12d499cb8c5490 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card