CVE-2026-43328

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path

When kobject_init_and_add() fails, cpufreq_dbs_governor_init() calls kobject_put(&dbs_data->attr_set.kobj).

The kobject release callback cpufreq_dbs_data_release() calls gov->exit(dbs_data) and kfree(dbs_data), but the current error path then calls gov->exit(dbs_data) and kfree(dbs_data) again, causing a double free.

Keep the direct kfree(dbs_data) for the gov->init() failure path, but after kobject_init_and_add() has been called, let kobject_put() handle the cleanup through cpufreq_dbs_data_release().

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
3.0%
KEV
Not listed

Published

May 8, 2026

Last Modified

June 1, 2026

Advisory Details (7)

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

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

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

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dcf9d0064ce2f3e3dfe5755f98b93abe6a98e1e
generic

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56bc91ee78babe9578585a2bc137abc4b3115ff3
generic

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/427d048e4f6acbfa01b5a8062449fe0ee8987c0d
generic

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bf9d023d2329a0e5379f2fd09d06ef09729cd9d
generic

cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/019ea28629720c220daedf38107c8787f330dc05

Vendor Advisories for CVE-2026-43328(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 111 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-43328?
CVE-2026-43328 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: cpufreq: governor: fix double free in cpufreqdbsgovernor_init() error path When kobjectinitandadd() fails, cpufreqdbsgovernorinit() calls kobjectput(&dbsdata->attr_set.kobj). The kobject release callback cpufreqdbsdata_release()…
When was CVE-2026-43328 disclosed?
CVE-2026-43328 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43328 actively exploited?
CVE-2026-43328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43328?
CVE-2026-43328 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43328, 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-43328

Explore →

Is Your Infrastructure Affected by CVE-2026-43328?

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

Start Free Scan →Browse All CVEs