In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: clean up ROC on failure
If the firmware fails to start the session protection, then we
do call iwl_mvm_roc_finished() here, but that won't do anything
at all because IWL_MVM_STATUS_ROC_P2P_RUNNING was never set.
Set IWL_MVM_STATUS_ROC_P2P_RUNNING in the failure/stop path.
If it started successfully before, it's already set, so that
doesn't matter, and if it didn't start it needs to be set to
clean up.
Not doing so will lead to a WARN_ON() later on a fresh remain-
on-channel, since the link is already active when activated as
it was never deactivated.
Metrics
Affected Vendors & Products
References
History
Fri, 23 May 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-665 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Wed, 02 Apr 2025 14:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Tue, 01 Apr 2025 16:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: clean up ROC on failure If the firmware fails to start the session protection, then we do call iwl_mvm_roc_finished() here, but that won't do anything at all because IWL_MVM_STATUS_ROC_P2P_RUNNING was never set. Set IWL_MVM_STATUS_ROC_P2P_RUNNING in the failure/stop path. If it started successfully before, it's already set, so that doesn't matter, and if it didn't start it needs to be set to clean up. Not doing so will lead to a WARN_ON() later on a fresh remain- on-channel, since the link is already active when activated as it was never deactivated. | |
Title | wifi: iwlwifi: mvm: clean up ROC on failure | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-04-01T15:40:47.059Z
Updated: 2025-05-04T07:23:56.656Z
Reserved: 2024-12-29T08:45:45.786Z
Link: CVE-2025-21906

No data.

Status : Awaiting Analysis
Published: 2025-04-01T16:15:21.110
Modified: 2025-04-01T20:26:01.990
Link: CVE-2025-21906
