SECUFOCUSNOW
Home›CVE index›CVE-2025-38421
Review reviewHigh

CVE-2025-38421

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: pmf: Use device managed allocations If setting up smart PC fails for any reason then this can lead to a double free when unloading amd-pmf. This is because dev->buf was freed but never set to NULL and is again freed in amd_pmf_remove(). To avoid subtle allocation bugs in failures leading to a double free change all allocations into device managed allocations.

CVSS
7.8
EPSS
0.15%
5.13% percentile
CISA KEV
Not listed
Published
2025.07.26
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd: pmf: Use device managed allocations If setting up smart PC fails for any reason then this can lead to a double free when unloading amd-pmf. This is because dev->buf was freed but never set to NULL and is again freed in amd_pmf_remove(). To avoid subtle allocation bugs in failures leading to a double free change all allocations into device managed allocations.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 5b1122fc4995f308b21d7cfc64ef9880ac834d20 < 0d10b532f861253c283863522d59d099fcb0796d, >= 5b1122fc4995f308b21d7cfc64ef9880ac834d20 < d9db3a941270d92bbd1a6a6b54a10324484f2f2d, >= e70b4b8f93d7fcf8ee063a1d1f18782c4da3d335, >= 3ed60e51ffdbfef14169bd967e21a6ba5e5ff42b, >= 6.12.23 < 6.13, >= 6.13.11 < 6.14, >= 6.14, >= 6.14.1 < 6.15.4, 6.14, 6.16
Fixed versions
6.13, 6.14, 6.15.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-415