padata: Fix pd UAF once and for all
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in a2048e475e22b13dc3e53d485b7e6e11464ed9a6; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in 73f132e60857038416540c3599b1de6033d7575a; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in 609e59193fc6d9dd323f1c6ae1fdd721f1c79680; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in a11a12a9880ab37342b73c93cfe1a3ada02ff0db; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in f231d5d001ec75f5886c02d496a4c79edc383d45; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in dbe3e911a59bda6de96e7cae387ff882c2c177fa; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in cdf79bd2e1ecb3cc75631c73d8f4149be6019a52; From 16295bec6398a3eedc9377e1af6ff4c71b98c300 · fixed in 71203f68c7749609d7fc8ae6ad054bdedeb24f91
- Linux Linux
2.6.34
- KernelLinux
From 2.6.34 · fixed in 5.10.258; From 5.11.0 · fixed in 5.15.209; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.86; From 6.13.0 · fixed in 6.15.10; From 6.16.0 · fixed in 6.16.1
References 8
git.kernel.org
- stable/c/a2048e475e22b13dc3e53d485b7e6e11464ed9a6
- stable/c/73f132e60857038416540c3599b1de6033d7575a
- stable/c/609e59193fc6d9dd323f1c6ae1fdd721f1c79680
- stable/c/a11a12a9880ab37342b73c93cfe1a3ada02ff0db
- stable/c/f231d5d001ec75f5886c02d496a4c79edc383d45
- stable/c/dbe3e911a59bda6de96e7cae387ff882c2c177fa
- stable/c/cdf79bd2e1ecb3cc75631c73d8f4149be6019a52
- stable/c/71203f68c7749609d7fc8ae6ad054bdedeb24f91