CVE-2025-38584
- Source
- https://cve.org/CVERecord?id=CVE-2025-38584
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-38584.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2025-38584
- Downstream
- Related
- Published
- 2025-08-19T17:03:06.172Z
- Modified
- 2026-03-20T12:42:55.600869Z
- Summary
- padata: Fix pd UAF once and for all
- Details
-
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 padatareorder that goes back to the initial commit. A reference count is taken at the start of the process in padatadoparallel, and released at the end in padataserial_worker.
This reference count is (and only is) required for padatareplace to function correctly. If padatareplace 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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38584.json", "cna_assigner": "Linux" }- References
-
- https://git.kernel.org/stable/c/71203f68c7749609d7fc8ae6ad054bdedeb24f91
- https://git.kernel.org/stable/c/cdf79bd2e1ecb3cc75631c73d8f4149be6019a52
- https://git.kernel.org/stable/c/dbe3e911a59bda6de96e7cae387ff882c2c177fa
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38584.json
- https://nvd.nist.gov/vuln/detail/CVE-2025-38584
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git