crypto: qat - resolve race condition during AER recovery
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c2cf5142bfb634c0ef0a1a69cdf37950747d0be, Kernel 226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7, Kernel 4ae5a97781ce7d6ecc9c7055396535815b64ca4f and 6 more.
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - resolve race condition during AER recovery During the PCI AER system's error recovery process, the kernel driver may encounter a race condition with freeing the reset_data structure's memory. If the device restart will take more than 10 seconds the function scheduling that restart will exit due to a timeout, and the reset_data structure will be freed. However, this data structure is used for completion notification after the restart is completed, which leads to a UAF bug. This results in a KFENCE bug notice. BUG: KFENCE: use-after-free read in adf_device_reset_worker+0x38/0xa0 [intel_qat] Use-after-free read at 0x00000000bc56fddf (in kfence-#142): adf_device_reset_worker+0x38/0xa0 [intel_qat] process_one_work+0x173/0x340 To resolve this race condition, the memory associated to the container of the work_struct is freed on the worker if the timeout expired, otherwise on the function that schedules the worker. The timeout detection can be done by checking if the caller is still waiting for completion or not by using completion_done() function.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.17, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <0c2cf5142bfb634c0ef0a1a69cdf37950747d0be, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <4ae5a97781ce7d6ecc9c7055396535815b64ca4f, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <7d42e097607c4d246d99225bf2b195b6167a210c, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <8a5a7611ccc7b1fba8d933a9f22a2e76859d94dc, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <8e81cd58aee14a470891733181a47d123193ba81, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <bb279ead42263e9fb09480f02a4247b2c287d828, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <d03092550f526a79cf1ade7f0dfa74906f39eb71, >=d8cba25d2c68992a6e7c1d329b690a9ebe01167d <daba62d9eeddcc5b1081be7d348ca836c83c59d7 | 0c2cf5142bfb634c0ef0a1a69cdf37950747d0be, 226fc408c5fcd23cc4186f05ea3a09a7a9aef2f7, 4ae5a97781ce7d6ecc9c7055396535815b64ca4f, 7d42e097607c4d246d99225bf2b195b6167a210c, 8a5a7611ccc7b1fba8d933a9f22a2e76859d94dc, 8e81cd58aee14a470891733181a47d123193ba81, bb279ead42263e9fb09480f02a4247b2c287d828, d03092550f526a79cf1ade7f0dfa74906f39eb71, daba62d9eeddcc5b1081be7d348ca836c83c59d7 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket