net: hns3: fix oops when unload drivers paralleling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0dd8a25f355b4df2d41c08df1716340854c7d4c5 · < cafe9a27e22736d4a01b3933e36225f9857c7988| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: hns3: fix oops when unload drivers paralleling
When unload hclge driver, it tries to disable sriov first for each ae_dev node from hnae3_ae_dev_list. If user unloads hns3 driver at the time, because it removes all the ae_dev nodes, and it may cause oops.
But we can't simply use hnae3_common_lock for this. Because in the process flow of pci_disable_sriov(), it will trigger the remove flow of VF, which will also take hnae3_common_lock.
To fixes it, introduce a new mutex to protect the unload process.
From the CVE record · Linux
The Linux kernel's hns3 network driver can trigger a kernel oops if the hns3 and hclge drivers are unloaded concurrently. The issue occurs during driver unloading; the input does not specify authentication requirements or affected versions.
Engineers running Linux kernels with the hns3 and hclge drivers should check their kernel versions against the vendor advisory.