LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58008: KEYS: trusted: dcp: fix improper sg use with CONFIG_VMAP_STACK=y

In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: dcp: fix improper sg use with CONFIG_VMAP_STACK=y With vmalloc stack addresses enabled (CONFIG_VMAP_STACK=y) DCP trusted keys can crash during en- and decryption of the blob encryption key via the DCP crypto driver. This is caused by improperly using sg_init_one() with vmalloc'd stack buffers (plain_key_blob). Fix this by always using kmalloc() for buffers we give to the DCP crypto driver.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems using DCP-backed trusted keys when a specific stack configuration is enabled. The known impact is availability and reliability, not documented data theft or remote compromise. Exposure appears narrow, but affected kernel builds should be updated through normal kernel maintenance channels.

Executive priority

Treat this as a targeted stability risk. Prioritize embedded, appliance, or platform systems that rely on Linux trusted keys and DCP hardware support, especially where kernel crashes affect service availability.

Technical view

DCP trusted keys used sg_init_one() on vmalloc-backed stack buffers when CONFIG_VMAP_STACK=y. The DCP crypto driver can crash during encryption or decryption of the blob encryption key. The stable fix uses kmalloc() for buffers passed to the DCP crypto driver.

Likely exposure

Likely limited to Linux systems on affected kernel versions that use DCP trusted keys with CONFIG_VMAP_STACK=y and the DCP crypto driver. Systems not using this trusted-key path are less likely exposed based on the provided sources.

Exploitation context

The source bundle reports no KEV listing and provides no cited evidence of active exploitation. The described failure mode is a kernel crash during trusted-key encryption or decryption, but exploitability beyond that is not established in the provided evidence.

Researcher notes

Evidence is limited to the CVE description and Linux stable commits. No CVSS, CWE, exploit status, or broader attack path is provided. The affected-version data appears branch-specific and should be reconciled against downstream vendor kernels.

Mitigation direction

  • Update to a kernel release or vendor package containing the stable fix.
  • Prioritize hosts using DCP trusted keys with CONFIG_VMAP_STACK=y.
  • Check Linux distribution and device vendor advisories for backported fixes.
  • Avoid relying on DCP trusted keys on affected kernels where operationally feasible.

Validation and detection

  • Identify kernel versions and compare them with vendor fixed-release guidance.
  • Confirm whether CONFIG_VMAP_STACK is enabled in deployed kernel builds.
  • Check whether DCP trusted keys and the DCP crypto driver are used.
  • Review kernel logs for crashes around trusted-key encryption or decryption.
Prepared
Confidence
medium
Sources
5

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-58008 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
4Source 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
LinuxLinux0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb, 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb, 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb, 9e3b266afcfe4294e84496f50f006f029d3100db, 6.10.7unaffected
LinuxLinux6.11, 0, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

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