CVE-2023-52836 Affecting kernel-syms-azure package, versions <6.4.0-150600.8.8.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-SLES156-KERNELSYMSAZURE-7679896
- published14 Aug 2024
- disclosed13 Aug 2024
Introduced: 13 Aug 2024
CVE-2023-52836 (opens in a new tab)How to fix?
Upgrade SLES:15.6 kernel-syms-azure to version 6.4.0-150600.8.8.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-syms-azure package and not the kernel-syms-azure package as distributed by SLES.
See How to fix? for SLES:15.6 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
locking/ww_mutex/test: Fix potential workqueue corruption
In some cases running with the test-ww_mutex code, I was seeing odd behavior where sometimes it seemed flush_workqueue was returning before all the work threads were finished.
Often this would cause strange crashes as the mutexes would be freed while they were being used.
Looking at the code, there is a lifetime problem as the controlling thread that spawns the work allocates the "struct stress" structures that are passed to the workqueue threads. Then when the workqueue threads are finished, they free the stress struct that was passed to them.
Unfortunately the workqueue work_struct node is in the stress struct. Which means the work_struct is freed before the work thread returns and while flush_workqueue is waiting.
It seems like a better idea to have the controlling thread both allocate and free the stress structures, so that we can be sure we don't corrupt the workqueue by freeing the structure prematurely.
So this patch reworks the test to do so, and with this change I no longer see the early flush_workqueue returns.
References
- https://www.suse.com/security/cve/CVE-2023-52836.html
- https://bugzilla.suse.com/1225609
- https://git.kernel.org/stable/c/304a2c4aad0fff887ce493e4197bf9cbaf394479
- https://git.kernel.org/stable/c/9ed2d68b3925145f5f51c46559484881d6082f75
- https://git.kernel.org/stable/c/bccdd808902f8c677317cec47c306e42b93b849e
- https://git.kernel.org/stable/c/c56df79d68677cf062da1b6e3b33e74299a92dfc
- https://git.kernel.org/stable/c/d4d37c9e6a4dbcca958dabd99216550525c7e389
- https://git.kernel.org/stable/c/d8267cabbe1bed15ccf8b0e684c528bf8eeef715
- https://git.kernel.org/stable/c/dcd85e3c929368076a7592b27f541e0da8b427f5
- https://git.kernel.org/stable/c/e36407713163363e65566e7af0abe207d5f59a0c
- https://git.kernel.org/stable/c/e89d0ed45a419c485bae999426ecf92697cbdda3