LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58075: crypto: tegra - do not transfer req when tegra init fails

In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - do not transfer req when tegra init fails The tegra_cmac_init or tegra_sha_init function may return an error when memory is exhausted. It should not transfer the request when they return an error.

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-58075 is a Linux kernel issue in Tegra crypto handling. If initialization fails, such as under memory exhaustion, the kernel should not continue transferring the crypto request. The public record gives no CVSS score, no CWE, and no confirmed real-world exploitation.

Executive priority

Treat this as targeted kernel hygiene rather than an emergency. Prioritize affected Tegra-based systems, especially embedded or appliance deployments, and fold remediation into the next kernel maintenance cycle unless vendor guidance raises severity.

Technical view

The flaw is in Linux kernel crypto tegra logic. tegra_cmac_init or tegra_sha_init can return an error when memory is exhausted, but the request may still be transferred. Stable kernel commits address this by avoiding request transfer after initialization failure.

Likely exposure

Exposure appears limited to affected Linux kernel builds using the Tegra crypto driver path. The bundle lists Linux as affected around versions 6.10, 6.12.13, 6.13.2, and 6.14, but version range details are incomplete.

Exploitation context

The source bundle does not cite active exploitation, public exploit activity, KEV listing, or a weaponized technique. The described trigger involves initialization failure during memory exhaustion, but operational impact is not quantified in the public data provided.

Researcher notes

Public evidence is sparse: no CVSS, CWE, exploit status, or detailed impact statement is provided. Analysis should stay anchored to the kernel commit behavior: failed tegra_cmac_init or tegra_sha_init must stop request transfer.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check distribution or device vendor advisories for supported patched packages.
  • Prioritize Tegra-based systems or kernels with Tegra crypto support enabled.
  • If patching is delayed, request vendor-supported temporary controls.

Validation and detection

  • Inventory Linux kernel versions across Tegra and embedded fleets.
  • Confirm whether Tegra crypto support is built, loaded, or used.
  • Check patched kernels for the referenced stable commit IDs.
  • Review vendor notices for backported fixes with different version numbers.
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-58075 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
LinuxLinux0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0, 0880bb3b00c855fc244b7177ffdaafef4d0aa1e0unaffected
LinuxLinux6.10, 0, 6.12.13, 6.13.2, 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.