First published: Tue May 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: padata: Fix refcnt handling in padata_free_shell() In a high-load arm64 environment, the pcrypt_aead01 test in LTP can lead to system UAF (Use-After-Free) issues. Due to the lengthy analysis of the pcrypt_aead01 function call, I'll describe the problem scenario using a simplified model: Suppose there's a user of padata named `user_function` that adheres to the padata requirement of calling `padata_free_shell` after `serial()` has been invoked, as demonstrated in the following code: ```c struct request { struct padata_priv padata; struct completion *done; }; void parallel(struct padata_priv *padata) { do_something(); } void serial(struct padata_priv *padata) { struct request *request = container_of(padata, struct request, padata); complete(request->done); } void user_function() { DECLARE_COMPLETION(done) padata->parallel = parallel; padata->serial = serial; padata_do_parallel(); wait_for_completion(&done); padata_free_shell(); } ``` In the corresponding padata.c file, there's the following code: ```c static void padata_serial_worker(struct work_struct *serial_work) { ... cnt = 0; while (!list_empty(&local_list)) { ... padata->serial(padata); cnt++; } local_bh_enable(); if (refcount_sub_and_test(cnt, &pd->refcnt)) padata_free_pd(pd); } ``` Because of the high system load and the accumulation of unexecuted softirq at this moment, `local_bh_enable()` in padata takes longer to execute than usual. Subsequently, when accessing `pd->refcnt`, `pd` has already been released by `padata_free_shell()`, resulting in a UAF issue with `pd->refcnt`. The fix is straightforward: add `refcount_dec_and_test` before calling `padata_free_pd` in `padata_free_shell`.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=3.16.84<3.17 | |
Linux Kernel | >=4.4.215<4.5 | |
Linux Kernel | >=4.9.215<4.10 | |
Linux Kernel | >=4.14.172<4.15 | |
Linux Kernel | >=4.19.103<4.20 | |
Linux Kernel | >=5.4.19<5.5 | |
Linux Kernel | >=5.5.3<5.10.201 | |
Linux Kernel | >=5.11<5.15.139 | |
Linux Kernel | >=5.16<6.1.63 | |
Linux Kernel | >=6.2<6.5.12 | |
Linux Kernel | >=6.6<6.6.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-52854 has a high severity rating due to its potential for causing use-after-free issues in high-load environments.
To fix CVE-2023-52854, update the Linux kernel to a version that includes the patch addressing this vulnerability.
CVE-2023-52854 affects multiple versions of the Linux kernel, including versions from 3.16.84 up to 6.6.2.
CVE-2023-52854 can lead to use-after-free vulnerabilities that may result in system crashes or arbitrary code execution.
CVE-2023-52854 specifically impacts arm64 architecture in high-load environments.