CVE-2025-38584

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 associated spin lock released, that padata may be processed and the reference count on pd would go away. Fix this by getting the next padata before the squeue->serial lock is released. In order to make this possible, simplify padata_reorder by only calling it once the next padata arrives.

CVSS 3.1

7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

0.2% chance of exploitation in the next 30 days; higher than 7% of CVEs (scores of 2026-10-25)

CWE

CWE-416

Published

2025-08-19

Modified

2026-10-15

Record from

the NVD, synced 2026-10-19

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/609e59193fc6d9dd323f1c6ae1fdd721f1c79680
• https://git.kernel.org/stable/c/71203f68c7749609d7fc8ae6ad054bdedeb24f91
• https://git.kernel.org/stable/c/73f132e60857038416540c3599b1de6033d7575a
• https://git.kernel.org/stable/c/a11a12a9880ab37342b73c93cfe1a3ada02ff0db
• https://git.kernel.org/stable/c/a2048e475e22b13dc3e53d485b7e6e11464ed9a6

Check your stackJSON