padata: avoid UAF for reorder_work
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bbefa1dd6a6d53537c11624752219e39959d04fb · < a54091c24220a4cd847d5b4f36d678edacddbaf0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
padata: avoid UAF for reorder_work
Although the previous patch can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF issue for reorder_work. This issue can happen just as below:
crypto_request crypto_request crypto_del_alg padata_do_serial ... padata_reorder // processes all remaining // requests then breaks while (1) { if (!padata) break; ... }
padata_do_serial // new request added list_add // sees the new request queue_work(reorder_work) padata_reorder queue_work_on(squeue->work) ...
<kworker context> padata_serial_worker // completes new request, // no more outstanding // requests
crypto_del_alg // free pd
<kworker context> invoke_padata_reorder // UAF of pd
From the CVE record · Linux
A race in the Linux kernel's padata reorder work can use freed memory when crypto requests overlap with algorithm deletion. The input does not specify how an attacker could trigger the race or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; the affected versions are not specified in the input.