Loading story…
CVE-2024-58075 affects the NVIDIA Tegra cryptographic driver in Linux kernels beginning with version 6.10. When tegra_cmac_init or tegra_sha_init fails—such as during memory exhaustion—the driver could still transfer the cryptographic request instead of stopping processing. The unchecked return value (CWE-252) can leave the system in an unexpected state and may cause crashes, restarts, or other availability impacts.
The issue is fixed in upstream stable kernels 6.12.13 and 6.13.2, and in Linux 6.14-rc1; maintainers recommend updating to a current stable kernel rather than cherry-picking the patch. Red Hat resolved the flaw for RHEL 9 and RHEL 10 through RHSA-2025:20518 and RHSA-2025:20095, respectively. Several older RHEL kernel streams are unaffected, while the RHEL 9 real-time kernel is designated will not fix.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Red Hat released RHSA-2025:20095 for the affected RHEL 10 kernel and RHSA-2025:20518 for the affected RHEL 9 kernel, addressing CVE-2024-58075.
The Linux kernel CVE team assigned CVE-2024-58075 to the Tegra crypto flaw. Remediations preventing transfer after failed initialization were included in Linux 6.12.13, 6.13.2, and 6.14-rc1.
A defect was introduced in Linux kernel 6.10 that allowed the NVIDIA Tegra crypto driver to transfer cryptographic requests after CMAC or SHA initialization failed, including under memory-exhaustion conditions.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
bugzilla.redhat.com
Open sourceredhat.com
Open sourcelore.kernel.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
CVE-2024-26638 is a low-severity flaw in the Linux kernel's Network Block Device (NBD) driver, introduced in kernel version 5.19. Incomplete initialization of a `struct msghdr` in the NBD reply-receive path can expose the uninitialized `msg_get_inq` field during `tcp_recvmsg` processing, triggering a KMSAN uninitialized-value error and affecting system availability. Exploitation requires local access and high privileges; Red Hat assigns a CVSS 3.1 score of 4.4. The upstream issue is fixed in Linux 6.1.76, 6.6.15, 6.7.3, 6.8, and later stable releases. Red Hat has issued fixes for affected Red Hat Enterprise Linux 8, RHEL 9, and RHEL 9.4 Extended Update Support packages, while RHEL 8 and RHEL 9 real-time kernels remain affected; unsupported RHEL 6 and 7 variants should be considered potentially affected. Organizations should update to vendor-supported current kernel releases rather than cherry-picking the individual upstream patch.
Aug 26, 2026
**CVE-2024-26939** is a use-after-free flaw in the Linux kernel's Intel i915 DRM graphics driver, in `drivers/gpu/drm/i915/i915_vma.c`. A race between i915 VMA destruction and asynchronous retirement can free a VMA while retirement logic still accesses it, allowing a local low-privileged attacker to crash the affected system. The vulnerability was introduced in Linux 5.19 and can produce debug-object warnings when a GPU GT is parked. The issue is fixed upstream in Linux kernel versions 6.1.88, 6.6.29, 6.8.3, and 6.9-rc2 and later stable releases. Red Hat has issued fixes for RHEL 8, RHEL 8 kernel-rt, RHEL 9, and RHEL 9.4 Extended Update Support; RHEL 9 kernel-rt is marked will not fix, while RHEL 6 and 7 variants are outside support scope. Red Hat rates the flaw Moderate at CVSS 5.5, compared with scores of 7.0 from NVD and 7.8 from CVE.org.
Aug 26, 2026
A flaw in the Linux kernel `crypto` `asymmetric_keys` subsystem, tracked as **CVE-2025-68724**, was fixed after maintainers found that `asymmetric_key_generate_id` could overflow while calculating the size of key identifier data derived from X.509 certificate fields. The bug affects kernels dating back to **3.18** and could trigger a buffer overflow when processing maliciously large certificate values, including ASN.1 INTEGER serial numbers and issuer names. Upstream kernel maintainers addressed the issue by adding `check_add_overflow()` validation and returning `ERR_PTR(-EOVERFLOW)` when oversized input is detected, with fixes released across multiple stable branches including **6.12.63**, **6.17.13**, **6.18.2**, and **6.19-rc1**. Red Hat published the vulnerability as a **Moderate** issue with a **CVSS 7.1** rating and shipped remediations through multiple RHEL 8, 9, and 10 kernel errata. One of the affected advisories, **RHSA-2026:23237**, delivered updated kernel packages for several **RHEL 9.4** SAP-related variants and included CVE-2025-68724 among a broader set of 12 kernel fixes; Red Hat said systems must be rebooted after installation for the updates to take effect. The vendor tied the flaw to **CWE-190** integer overflow and advised customers to apply the updated kernel packages rather than rely on partial fixes.
Aug 25, 2026