Race Condition Affecting kernel-obs-build package, versions <5.14.21-150400.24.133.2
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-SLES154-KERNELOBSBUILD-8090385
- published25 Sept 2024
- disclosed24 Sept 2024
Introduced: 24 Sep 2024
CVE-2022-48941 (opens in a new tab)How to fix?
Upgrade SLES:15.4 kernel-obs-build to version 5.14.21-150400.24.133.2 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-obs-build package and not the kernel-obs-build package as distributed by SLES.
See How to fix? for SLES:15.4 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
ice: fix concurrent reset and removal of VFs
Commit c503e63200c6 ("ice: Stop processing VF messages during teardown") introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is intended to prevent some issues with concurrently handling messages from VFs while tearing down the VFs.
This change was motivated by crashes caused while tearing down and bringing up VFs in rapid succession.
It turns out that the fix actually introduces issues with the VF driver caused because the PF no longer responds to any messages sent by the VF during its .remove routine. This results in the VF potentially removing its DMA memory before the PF has shut down the device queues.
Additionally, the fix doesn't actually resolve concurrency issues within the ice driver. It is possible for a VF to initiate a reset just prior to the ice driver removing VFs. This can result in the remove task concurrently operating while the VF is being reset. This results in similar memory corruption and panics purportedly fixed by that commit.
Fix this concurrency at its root by protecting both the reset and removal flows using the existing VF cfg_lock. This ensures that we cannot remove the VF while any outstanding critical tasks such as a virtchnl message or a reset are occurring.
This locking change also fixes the root cause originally fixed by commit c503e63200c6 ("ice: Stop processing VF messages during teardown"), so we can simply revert it.
Note that I kept these two changes together because simply reverting the original commit alone would leave the driver vulnerable to worse race conditions.
References
- https://www.suse.com/security/cve/CVE-2022-48941.html
- https://bugzilla.suse.com/1229614
- https://git.kernel.org/stable/c/05ae1f0fe9c6c5ead08b306e665763a352d20716
- https://git.kernel.org/stable/c/2a3e61de89bab6696aa28b70030eb119968c5586
- https://git.kernel.org/stable/c/3c805fce07c9dbc47d8a9129c7c5458025951957
- https://git.kernel.org/stable/c/fadead80fe4c033b5e514fcbadd20b55c4494112