CVE-2024-50136: net/mlx5: Unregister notifier on eswitch init failure
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Unregister notifier on eswitch init failure
It otherwise remains registered and a subsequent attempt at eswitch enabling might trigger warnings of the sort:
[ 682.589148] ------------[ cut here ]------------ [ 682.590204] notifier callback eswitchvportevent [mlx5core] already registered [ 682.590256] WARNING: CPU: 13 PID: 2660 at kernel/notifier.c:31 notifierchainregister+0x3e/0x90 [...snipped] [ 682.610052] Call Trace: [ 682.610369] <TASK> [ 682.610663] ? warn+0x7c/0x110 [ 682.611050] ? notifierchainregister+0x3e/0x90 [ 682.611556] ? reportbug+0x148/0x170 [ 682.611977] ? handlebug+0x36/0x70 [ 682.612384] ? excinvalidop+0x13/0x60 [ 682.612817] ? asmexcinvalidop+0x16/0x20 [ 682.613284] ? notifierchainregister+0x3e/0x90 [ 682.613789] atomicnotifierchainregister+0x25/0x40 [ 682.614322] mlx5eswitchenablelocked+0x1d4/0x3b0 [mlx5core] [ 682.614965] mlx5eswitchenable+0xc9/0x100 [mlx5core] [ 682.615551] mlx5deviceenablesriov+0x25/0x340 [mlx5core] [ 682.616170] mlx5coresriovconfigure+0x50/0x170 [mlx5core] [ 682.616789] sriovnumvfsstore+0xb0/0x1b0 [ 682.617248] kernfsfopwriteiter+0x117/0x1a0 [ 682.617734] vfswrite+0x231/0x3f0 [ 682.618138] ksyswrite+0x63/0xe0 [ 682.618536] dosyscall64+0x4c/0x100 [ 682.618958] entrySYSCALL64afterhwframe+0x4b/0x53
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50136?
CVE-2024-50136 is classified as a moderate severity vulnerability affecting the Linux kernel.
What versions of the Linux kernel are affected by CVE-2024-50136?
CVE-2024-50136 affects Linux kernel versions from 6.1.60 to 6.1.115, 6.5.9 to 6.6, and several other specific release candidates.
How do I fix CVE-2024-50136?
To fix CVE-2024-50136, you should update your Linux kernel to a version that has resolved this vulnerability.
What can happen if CVE-2024-50136 is not addressed?
If CVE-2024-50136 is not addressed, it may lead to warnings during eswitch enabling attempts and potential operational issues.
Is there a workaround for CVE-2024-50136 until a fix is applied?
There is no specific workaround for CVE-2024-50136; it is advisable to apply the appropriate kernel updates as soon as possible.