LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43328: cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path

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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-43328 is a Linux kernel bug in CPU frequency governor initialization. In one failure path, memory cleanup can run twice, creating a double free. That can destabilize a kernel and may create memory-corruption risk, but the bundle does not state a proven exploit path or business-impact scope.

Executive priority

Handle through normal-to-accelerated kernel patch management. There is no source-backed evidence of active exploitation, but kernel double-free bugs can affect system stability and are expensive to recover from if triggered on critical hosts.

Technical view

The bug is in cpufreq_dbs_governor_init(). If kobject_init_and_add() fails, kobject_put() invokes cpufreq_dbs_data_release(), which calls gov->exit(dbs_data) and kfree(dbs_data). The old error path then repeated gov->exit() and kfree(), causing double free. The fix lets kobject release handling own cleanup after kobject initialization.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor builds containing the vulnerable cpufreq governor code. The source bundle lists Linux as affected across multiple kernel lines, but does not map this to specific distributions, appliances, cloud images, or default configurations.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the bundle provides no exploit prerequisites, attacker position, or trigger reliability. Treat exploitability as unconfirmed until Linux or distribution vendors publish more detailed advisories.

Researcher notes

Evidence is limited: no CVSS, CWE, CPEs, exploit status, or distribution mapping are provided. The root cause and fix direction are clear from the CVE description and stable commit references, but practical trigger conditions and security impact remain unspecified.

Mitigation direction

  • Apply Linux or distribution kernel updates that include the referenced stable fixes.
  • Prioritize shared, high-availability, and sensitive Linux hosts for earlier kernel maintenance.
  • If no vendor package is available, track vendor guidance before applying custom kernels.
  • Reboot systems as required for the fixed kernel to become active.

Validation and detection

  • Inventory Linux kernel versions across affected servers and images.
  • Confirm vendor changelogs include CVE-2026-43328 or the relevant stable commit.
  • Verify running kernels after maintenance, not only installed kernel packages.
  • Check fleet exceptions where kernel pinning may block security updates.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43328 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, 4ebe36c94aed95de71a8ce6a6762226d31c938ee, e977b1477a6725868302957e6b5c330220391797, 5.1.6unaffected
LinuxLinux5.2, 0, 5.10.253, 5.15.209, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.