LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42147: crypto: hisilicon/debugfs - Fix debugfs uninit process issue

In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/debugfs - Fix debugfs uninit process issue During the zip probe process, the debugfs failure does not stop the probe. When debugfs initialization fails, jumping to the error branch will also release regs, in addition to its own rollback operation. As a result, it may be released repeatedly during the regs uninit process. Therefore, the null check needs to be added to the regs uninit process.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in HiSilicon crypto debugfs cleanup. If debugfs setup fails during ZIP driver probing, the kernel may release the same register resource more than once. The source bundle does not provide CVSS, impact detail, or evidence of active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize systems with HiSilicon acceleration hardware or affected vendor kernels, and fold remediation into normal kernel patch cycles unless vendor guidance raises severity.

Technical view

The issue is in crypto: hisilicon/debugfs. During ZIP probe, debugfs failure does not stop probing cleanly; error handling can release regs in both rollback and uninit paths. The fix adds a null check in regs uninit to prevent repeated release.

Likely exposure

Exposure appears limited to Linux systems using the affected HiSilicon ZIP crypto driver/debugfs path. The bundle lists Linux kernel versions and stable commits, but provides no CPEs, asset guidance, or complete configuration prerequisites.

Exploitation context

CISA KEV status is false in the bundle, and no cited source reports active exploitation. The public description indicates a cleanup/resource-management flaw, but does not describe attacker prerequisites or practical exploitability.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploitability analysis, or CPEs are supplied. Analysis should focus on affected kernel branches, backport status, and whether the vulnerable probe/error path is reachable on deployed HiSilicon ZIP configurations.

Mitigation direction

  • Update Linux kernels through your distribution or vendor when fixes include the referenced stable commits.
  • If using Debian LTS, review and apply the Debian LTS kernel update referenced in the advisory.
  • Prioritize vendor-supported kernel packages over manual kernel patching.
  • If patching is delayed, ask the platform vendor for supported operational mitigations.

Validation and detection

  • Inventory Linux systems that use HiSilicon ZIP crypto hardware or related kernel modules.
  • Compare running kernel builds against vendor advisories and the referenced stable commits.
  • Confirm patched systems include the regs uninit null-check fix.
  • Review kernel and distribution advisory notes for backported fix status.
Prepared
Confidence
medium
Sources
7

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-42147 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
6Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux263c9959c9376ec0217d6adc61222a53469eed3c, 263c9959c9376ec0217d6adc61222a53469eed3c, 263c9959c9376ec0217d6adc61222a53469eed3c, 263c9959c9376ec0217d6adc61222a53469eed3cunaffected
LinuxLinux5.4, 0, 6.1.98, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

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