CVE-2022-48941: In the Linux kernel, the following vulnerability has been resolved: ice: fix concurrent reset and removal of VFs Commit c503e63200c6 ("ice: Stop processing VF…

PriorityP417medium4.7CVSS 3.1

AVLACHPRLUINSUCNINAH

EPSS

0.17%

6.9th percentile

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.

Affected

13 ranges

Vendor	Product	Version range	Fixed in
debian	linux	< linux 5.16.12-1 (bookworm)	linux 5.16.12-1 (bookworm)
linux	linux	—	—
linux	linux	—	—
linux	linux	>= 5.13.12 < 5.14	5.14
linux	linux	>= c503e63200c679e362afca7aca9d3dc63a0f45ed < 3c805fce07c9dbc47d8a9129c7c5458025951957	3c805fce07c9dbc47d8a9129c7c5458025951957
linux	linux	>= c503e63200c679e362afca7aca9d3dc63a0f45ed < 2a3e61de89bab6696aa28b70030eb119968c5586	2a3e61de89bab6696aa28b70030eb119968c5586
linux	linux	>= c503e63200c679e362afca7aca9d3dc63a0f45ed < fadead80fe4c033b5e514fcbadd20b55c4494112	fadead80fe4c033b5e514fcbadd20b55c4494112
linux	linux_kernel	< 5.10.104	5.10.104
linux	linux_kernel	>= 0 < 5.16.12-1	5.16.12-1
linux	linux_kernel	>= 0 < 5.16.12-1	5.16.12-1
linux	linux_kernel	>= 0 < 5.16.12-1	5.16.12-1
linux	linux_kernel	>= 5.11 < 5.15.26	5.15.26
linux	linux_kernel	>= 5.16 < 5.16.12	5.16.12

CVSS provenance

nvdv3.14.7MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

osv4.7MEDIUM

vendor_debian4.7MEDIUM

vendor_redhat4.7MEDIUM

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.