LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38609: PM / devfreq: Check governor before using governor->name

In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Check governor before using governor->name Commit 96ffcdf239de ("PM / devfreq: Remove redundant governor_name from struct devfreq") removes governor_name and uses governor->name to replace it. But devfreq->governor may be NULL and directly using devfreq->governor->name may cause null pointer exception. Move the check of governor to before using governor->name.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-38609 is a Linux kernel devfreq power-management bug. A kernel change removed a stored governor name and then used governor->name even when the governor pointer could be null, causing a possible null pointer exception. Sources do not provide CVSS, confirmed exploitability, or observed exploitation.

Executive priority

Treat as routine-to-priority kernel maintenance, not an emergency based on current evidence. Raise priority for embedded, mobile, or infrastructure systems where kernel crashes would create availability impact.

Technical view

The flaw is in Linux PM/devfreq logic after commit 96ffcdf239de. Code dereferenced devfreq->governor->name before confirming devfreq->governor was non-null. Upstream stable fixes move the governor null check before name access across multiple kernel branches.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or downstream builds carrying the vulnerable devfreq change. Systems with kernels fixed by the referenced stable commits or vendor updates should not be treated as exposed.

Exploitation context

The provided sources do not show active exploitation, proof-of-concept availability, or KEV listing. The documented impact is a potential kernel null pointer exception; practical exploitability depends on reachable devfreq code paths and platform configuration.

Researcher notes

The record lacks CVSS, CWE, and exploit detail. Analysis should focus on affected kernel lineage and whether devfreq governor handling is reachable on the target platform. Do not infer remote exploitation from the provided sources.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Follow Linux distribution advisories, including Debian LTS where applicable.
  • Prioritize systems using affected kernel branches or custom kernels.
  • Check vendor guidance before applying source-level backports.
  • Avoid assuming mitigation beyond the published kernel fix.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Check whether builds include commit 96ffcdf239de without the fix.
  • Confirm patched kernels include the relevant stable commit.
  • Review distribution security advisories for packaged kernel status.
  • Monitor fleet telemetry for kernel null pointer exceptions in devfreq paths.
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-2025-38609 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
1ADP 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.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9, 96ffcdf239de6f9970178bb7d643e16fd9e68ab9unaffected
LinuxLinux5.11, 0, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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