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

CVE-2025-38584

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: padata: Fix pd UAF once and for all There is a race condition/UAF in padata_reorder that goes back to the initial commit. A reference count is taken at the start of the process in padata_do_parallel, and released at the end in padata_serial_worker. This reference count is (and only is) required for padata_replace to function correctly. If padata_replace is never called then there is no issue. In the function padata_reorder which serves as the core of padata, as soon as padata is added to queue->serial.list, and the associat...

CVSS
7.8
EPSS
0.16%
6.02% percentile
CISA KEV
Not listed
Published
2025.08.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: padata: Fix pd UAF once and for all There is a race condition/UAF in padata_reorder that goes back to the initial commit. A reference count is taken at the start of the process in padata_do_parallel, and released at the end in padata_serial_worker. This reference count is (and only is) required for padata_replace to function correctly. If padata_replace is never called then there is no issue. In the function padata_reorder which serves as the core of padata, as soon as padata is added to queue->serial.list, and the associat...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < a2048e475e22b13dc3e53d485b7e6e11464ed9a6, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < 73f132e60857038416540c3599b1de6033d7575a, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < 609e59193fc6d9dd323f1c6ae1fdd721f1c79680, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < a11a12a9880ab37342b73c93cfe1a3ada02ff0db, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < f231d5d001ec75f5886c02d496a4c79edc383d45, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < dbe3e911a59bda6de96e7cae387ff882c2c177fa, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < cdf79bd2e1ecb3cc75631c73d8f4149be6019a52, >= 16295bec6398a3eedc9377e1af6ff4c71b98c300 < 71203f68c7749609d7fc8ae6ad054bdedeb24f91, >= 2.6.34, >= 2.6.34 < 6.15.10, >= 6.16 < 6.16.1
Fixed versions
6.15.10, 6.16.1

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-416