CVE-2026-74519

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

pinctrl: devicetree: don't free uninitialized dev_name on error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ad0ad3c228b6f76fde10f32047e0ec5fbc109dc8
generic

pinctrl: devicetree: don't free uninitialized dev_name on error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d00a5ac7cd3d32ae61140f4b8a62f136de84e7d
generic

pinctrl: devicetree: don't free uninitialized dev_name on error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/929f6396baade89999ec8a1281232c101cbc727d
generic

pinctrl: devicetree: don't free uninitialized dev_name on error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/321fe3584a8298386938130d138191aa35040b75
generic

pinctrl: devicetree: don't free uninitialized dev_name on error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/015b5bcbcb622b32317642be91a7f79aa5413649

Vendor Advisories for CVE-2026-74519(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 30× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 18:54 UTCGHSA enrichment
  3. 2026-08-20 06:17 UTCGHSA enrichment
  4. 2026-08-19 17:38 UTCEG score recompute
  5. 2026-08-19 17:38 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:53 UTCEG score recompute
  8. 2026-08-19 16:53 UTCGHSA enrichment
  9. 2026-08-19 08:59 UTCGHSA enrichment
  10. 2026-08-18 20:20 UTCEG score recompute
  11. 2026-08-18 20:20 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 07:43 UTCGHSA enrichment
  15. 2026-08-17 19:02 UTCEG score recompute
  16. 2026-08-17 19:02 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:24 UTCEG score recompute
  19. 2026-08-17 06:24 UTCGHSA enrichment
  20. 2026-08-17 05:55 UTCEG score recompute▲ 7.80
  21. 2026-08-17 05:55 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-08-17 05:39 UTCEG score recompute
  24. 2026-08-17 05:39 UTCGHSA enrichment
  25. 2026-08-17 05:39 UTCMITRE cvelistV5
Show 5 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-15 13:27 UTCNVD update
  4. 2026-08-15 12:39 UTCEG score recompute
  5. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74519?
CVE-2026-74519 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: don't free uninitialized dev_name on error path dtrememberorfreemap() duplicates dev_name for each map entry. If kstrdupconst() fails, dtfreemap() frees devname in all num_maps entries, including entries that…
When was CVE-2026-74519 disclosed?
CVE-2026-74519 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74519 actively exploited?
CVE-2026-74519 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.6% of all scored CVEs.
What is the CVSS score of CVE-2026-74519?
CVE-2026-74519 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74519?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74519, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74519

Explore →

Is Your Infrastructure Affected by CVE-2026-74519?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs