LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27051: cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value

In the Linux kernel, the following vulnerability has been resolved: cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return 0 in case of error. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-27051 is a Linux kernel flaw in the Broadcom STB AVS CPU frequency driver. A missing NULL check could cause a kernel NULL-pointer dereference, likely resulting in a system crash rather than data theft. Public sources do not provide CVSS, exploitability, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch management, with higher priority for Broadcom STB-based Linux devices. Current public evidence supports availability-risk concern, not confirmed compromise or data exposure.

Technical view

The flaw is in brcmstb-avs-cpufreq. cpufreq_cpu_get() can return NULL, and the driver previously did not check that return value. Stable kernel fixes add the check and return safely on error. The CVE record lists Linux kernel versions from 4.10 and affected stable branches until fixed releases.

Likely exposure

Exposure is most relevant to Linux systems using the brcmstb-avs-cpufreq driver, commonly tied to Broadcom STB platforms. Generic Linux servers may not include or use this driver. Confirm kernel branch, vendor backports, and whether the driver is built or active.

Exploitation context

No CISA KEV listing is present, and the provided sources do not report active exploitation. The public description indicates a NULL dereference condition. Practical exploitability, required privileges, and attack surface are not defined in the sources.

Researcher notes

The CVE is sparse: no CVSS, CWE, proof-of-concept, or detailed trigger path is provided. The fix is a defensive NULL check in the cpufreq driver. Assess reachability by kernel configuration and platform hardware support.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • For Debian LTS systems, review the cited Debian advisory and apply applicable updates.
  • If patching is delayed, check vendor guidance for platform-specific mitigations.
  • Prioritize systems where the brcmstb-avs-cpufreq driver is present or active.

Validation and detection

  • Inventory Linux kernel versions and vendor package release levels.
  • Check whether brcmstb-avs-cpufreq is built into the kernel or available as a module.
  • Map installed kernels against the referenced fixed stable commits or distro advisories.
  • Confirm remediation through vendor package metadata, not only upstream version numbers.
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-2024-27051 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
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxde322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163, de322e085995b9417582d6f72229dadb5c09d163unaffected
LinuxLinux4.10, 0, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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