CVE-2026-74519

CVE CVE-2026-74519EUVD EUVD-2026-59712Published 2026-08-15T12:27:38.000ZLast changed 2026-08-19T16:38:21.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux be4c60b563edee3712d392aaeb0943a768df7023 <dec5f0a8080502908dec5e35597c7ae07d533a3b; be4c60b563edee3712d392aaeb0943a768df7023 <ad0ad3c228b6f76fde10f32047e0ec5fbc109dc8; 4.9.244 <4.10; 4.4.244 <4.5; 679c4f27b8958b65bb51d1c3dfdbf3befe4a33a3; 03f69244302d7954f42f528ea2d45903ebbf59f3; patch: 6.6.151; be4c60b563edee3712d392aaeb0943a768df7023 <015b5bcbcb622b32317642be91a7f79aa5413649; 5.4.7 <5.5; patch: 6.12.103; patch: 5.15.216; patch: 6.1.183; f739a699db7d5a5cf39ca3ce2c84e4fe4a8f4c5d; patch: 6.18.44; patch: 5.10.265; 77440c3a37203e3f4667d06e37f76ef3968d2d8c; be4c60b563edee3712d392aaeb0943a768df7023 <e3cfb22bad363bebcfd55d909e12d499cb8c5490; 4.19.92 <4.20; be4c60b563edee3712d392aaeb0943a768df7023 <9d00a5ac7cd3d32ae61140f4b8a62f136de84e7d; patch: 7.1.8; patch: 0; be4c60b563edee3712d392aaeb0943a768df7023 <929f6396baade89999ec8a1281232c101cbc727d; be4c60b563edee3712d392aaeb0943a768df7023 <321fe3584a8298386938130d138191aa35040b75; 5.5; f88ac1330779c5bfdd79f7d7f7d4d3343c782f92; patch: 7.2; 4.14.161 <4.15; be4c60b563edee3712d392aaeb0943a768df7023 <1586423da2739a80871ef6240016fcb9c7339bfb

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.