LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27039: clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()

In the Linux kernel, the following vulnerability has been resolved: clk: hisilicon: hi3559a: Fix an erroneous devm_kfree() 'p_clk' is an array allocated just before the for loop for all clk that need to be registered. It is incremented at each loop iteration. If a clk_register() call fails, 'p_clk' may point to something different from what should be freed. The best we can do, is to avoid this wrong release of memory.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-27039 is a Linux kernel bug in the HiSilicon HI3559A clock driver. If clock registration fails, the driver may free the wrong memory pointer. The public record does not provide CVSS, proven impact, or evidence of exploitation, so urgency depends on whether affected kernels and this hardware driver exist in your environment.

Executive priority

Treat this as a targeted kernel hygiene issue unless asset inventory shows affected HiSilicon HI3559A systems. There is no cited exploitation or severity score, but kernel memory-management defects warrant timely patch tracking in embedded or appliance environments.

Technical view

The flaw is in the Linux kernel clk hisilicon hi3559a code. An allocated clock pointer array is incremented during registration, and an error path may call devm_kfree() on the wrong pointer. The kernel fix avoids the incorrect memory release. The source bundle lists affected Linux kernel versions and stable commit references, but no CWE or CVSS.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the HiSilicon HI3559A clock driver present or relevant. The bundle lists Linux as affected, with kernel version data and stable fixes, but does not identify distributions, appliances, or cloud services.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not listed as KEV. The bundle does not describe exploitability, attacker prerequisites, or security impact beyond the erroneous memory free during a driver failure path.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. The vulnerable behavior is an erroneous devm_kfree() after pointer advancement in the failure path. Do not infer affected distributions, exploit primitives, or remote attack paths from the supplied sources alone.

Mitigation direction

  • Update to a vendor-supported Linux kernel containing the referenced stable fix.
  • Check Linux distribution advisories for packaged kernel status and backports.
  • Prioritize systems using HiSilicon HI3559A support or affected kernel branches.
  • If unused, consider excluding the driver through normal kernel configuration review.
  • Avoid direct deployment shortcuts; follow standard kernel change control and rollback planning.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Confirm whether HI3559A clock driver support is built or deployed.
  • Verify patched kernels include one applicable stable commit from the references.
  • Check vendor changelogs for CVE-2024-27039 backport confirmation.
  • Document systems where hardware or driver exposure is absent.
Prepared
Confidence
medium
Sources
8

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-27039 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
7Source 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
LinuxLinux6c81966107dc0caa5d2ebedbcebb5f10d865064d, 6c81966107dc0caa5d2ebedbcebb5f10d865064d, 6c81966107dc0caa5d2ebedbcebb5f10d865064d, 6c81966107dc0caa5d2ebedbcebb5f10d865064d, 6c81966107dc0caa5d2ebedbcebb5f10d865064d, 6c81966107dc0caa5d2ebedbcebb5f10d865064dunaffected
LinuxLinux5.14, 0, 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.