CVE-2026-43196

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

soc: ti: pruss: Fix double free in pruss_clk_mux_setup()

In the pruss_clk_mux_setup(), the devm_add_action_or_reset() indirectly calls pruss_of_free_clk_provider(), which calls of_node_put(clk_mux_np) on the error path. However, after the devm_add_action_or_reset() returns, the of_node_put(clk_mux_np) is called again, causing a double free.

Fix by returning directly, to avoid the duplicate of_node_put().

CVSS v3
7.8
EG Score
7.8(medium)
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

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (8)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

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

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/818cf66d91c8ef09b01664a12d5f4ea786d64396
generic

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80db65d4acfb9ff12d00172aed39ea8b98261aad
generic

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69aa67c1e22d13e9aad4b08c86304ad8e743dcab
generic

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24c40076e3bc3d73c839c886d6bda1da6c4d9b93
generic

soc: ti: pruss: Fix double free in pruss_clk_mux_setup() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04dbbb18cc9c8795c9ff47d8994bc03ebfef9d68

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1055.56~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 26× 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.

Showing the most recent 100 of 210 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 16:23 UTCOSV refresh
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-23 20:02 UTCEG score recompute
  23. 2026-08-23 20:02 UTCVendor advisory
  24. 2026-08-23 20:02 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 12:56 UTCEG score recompute
  7. 2026-08-17 12:56 UTCVendor advisory
  8. 2026-08-17 12:56 UTCGHSA enrichment
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 04:53 UTCEG score recompute
  11. 2026-08-16 04:53 UTCVendor advisory
  12. 2026-08-16 04:53 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 16:22 UTCVendor advisory
  16. 2026-08-14 16:22 UTCGHSA enrichment
  17. 2026-08-14 03:28 UTCEG score recompute
  18. 2026-08-14 03:28 UTCVendor advisory
  19. 2026-08-14 03:28 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 06:07 UTCVendor advisory
  22. 2026-08-13 06:07 UTCGHSA enrichment
  23. 2026-08-12 17:01 UTCEG score recompute
  24. 2026-08-12 17:01 UTCVendor advisory
  25. 2026-08-12 17:01 UTCGHSA enrichment
  26. 2026-08-12 13:51 UTCEPSS rescore
  27. 2026-08-11 16:00 UTCEG score recompute
  28. 2026-08-11 16:00 UTCVendor advisory
  29. 2026-08-11 16:00 UTCGHSA enrichment
  30. 2026-08-11 13:43 UTCEPSS rescore
  31. 2026-08-11 01:32 UTCEG score recompute
  32. 2026-08-11 01:32 UTCVendor advisory
  33. 2026-08-11 01:32 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 04:25 UTCVendor advisory
  36. 2026-08-10 04:25 UTCGHSA enrichment
  37. 2026-08-09 15:30 UTCEG score recompute
  38. 2026-08-09 15:30 UTCVendor advisory
  39. 2026-08-09 15:30 UTCGHSA enrichment
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-09 02:36 UTCEG score recompute
  42. 2026-08-09 02:36 UTCVendor advisory
  43. 2026-08-09 02:36 UTCGHSA enrichment
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-08 03:43 UTCVendor advisory
  46. 2026-08-08 03:43 UTCGHSA enrichment
  47. 2026-08-07 14:49 UTCVendor advisory
  48. 2026-08-07 14:48 UTCGHSA enrichment
  49. 2026-08-07 01:54 UTCEG score recompute
  50. 2026-08-07 01:54 UTCVendor advisory
  51. 2026-08-07 01:54 UTCGHSA enrichment
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 11:19 UTCVendor advisory
  54. 2026-08-06 11:19 UTCGHSA enrichment
  55. 2026-08-05 22:21 UTCEG score recompute
  56. 2026-08-05 22:21 UTCVendor advisory
  57. 2026-08-05 22:21 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:38 UTCEPSS rescore
  61. 2026-08-03 19:52 UTCEG score recompute
  62. 2026-08-03 19:52 UTCVendor advisory
  63. 2026-08-03 19:52 UTCGHSA enrichment
  64. 2026-08-03 10:36 UTCEPSS rescore
  65. 2026-08-02 18:02 UTCVendor advisory
  66. 2026-08-02 18:02 UTCGHSA enrichment
  67. 2026-08-02 05:08 UTCEG score recompute
  68. 2026-08-02 05:08 UTCVendor advisory
  69. 2026-08-02 05:08 UTCGHSA enrichment
  70. 2026-08-02 02:27 UTCEPSS rescore
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-30 16:28 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-28 15:36 UTCEPSS rescore
  75. 2026-07-27 14:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43196?
CVE-2026-43196 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: soc: ti: pruss: Fix double free in prussclkmux_setup() In the prussclkmuxsetup(), the devmaddactionor_reset() indirectly calls prussoffreeclkprovider(), which calls ofnodeput(clkmuxnp) on the error path. However, after the…
When was CVE-2026-43196 disclosed?
CVE-2026-43196 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43196 actively exploited?
CVE-2026-43196 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 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-43196?
CVE-2026-43196 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43196?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43196, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43196

Explore →

Is Your Infrastructure Affected by CVE-2026-43196?

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