CVE-2024-36281: net/mlx5: Use mlx5_ipsec_rx_status_destroy to correctly delete status rules
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Use mlx5ipsecrxstatusdestroy to correctly delete status rules
rxcreate no longer allocates a modifyhdr instance that needs to be cleaned up. The mlx5modifyheaderdealloc call will lead to a NULL pointer dereference. A leak in the rules also previously occurred since there are now two rules populated related to status.
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: errorcode(0x0000) - not-present page PGD 109907067 P4D 109907067 PUD 116890067 PMD 0 Oops: 0000 [#1] SMP CPU: 1 PID: 484 Comm: ip Not tainted 6.9.0-rc2-rrameshbabu+ #254 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:mlx5modifyheaderdealloc+0xd/0x70 <snip> Call Trace: <TASK> ? showregs+0x60/0x70 ? die+0x24/0x70 ? pagefaultoops+0x15f/0x430 ? freetopartiallist.constprop.0+0x79/0x150 ? douseraddrfault+0x2c9/0x5c0 ? excpagefault+0x63/0x110 ? asmexcpagefault+0x27/0x30 ? mlx5modifyheaderdealloc+0xd/0x70 rxcreate+0x374/0x590 rxaddrule+0x3ad/0x500 ? rxaddrule+0x3ad/0x500 ? mlx5cmdexec+0x2c/0x40 ? mlx5createipsecobj+0xd6/0x200 mlx5eaccelipsecfsaddrule+0x31/0xf0 mlx5exfrmaddstate+0x426/0xc00 <snip>
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-36281?
CVE-2024-36281 has been categorized as a moderate severity vulnerability affecting the Linux kernel.
What versions of the Linux kernel are affected by CVE-2024-36281?
CVE-2024-36281 affects Linux kernel versions between 6.6.8 and 6.6.33, 6.7 and 6.9.4, and specifically version 6.10-rc2.
How can I fix CVE-2024-36281?
To remediate CVE-2024-36281, update to the patched versions of the Linux kernel, such as 5.10.223-1, 6.1.123-1, or 6.12.12-1.
What is the impact of CVE-2024-36281?
The impact of CVE-2024-36281 relates to improper memory management in the Linux kernel, which could lead to resource leaks.
Is there a workaround for CVE-2024-36281 if I cannot update immediately?
Currently, there are no known workarounds for CVE-2024-36281, so it is highly recommended to apply the updates as soon as possible.