Menu

Star on GitHub · 3.2k

CVE-2025-40338

In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: avs: Do not share the name pointer between components By sharing 'name' directly, tearing down components may lead…

Published Dec 9, 2025EPSS 0.21%

Overview

CVE-2025-40338 is a known-severity vulnerability. It was published on December 9, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: Intel: avs: Do not share the name pointer between components

By sharing 'name' directly, tearing down components may lead to

use-after-free errors. Duplicate the name to avoid that.

At the same time, update the order of operations - since commit

cee28113db17 ("ASoC: dmaengine_pcm: Allow passing component name via

config") the framework does not override component->name if set before

invoking the initializer.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-40338?

CVE-2025-40338 is a known-severity vulnerability. It was published on December 9, 2025.

How severe is CVE-2025-40338?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-40338?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-40338?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-40338 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.