CVE-2024-46737: nvmet-tcp: fix kernel crash if commands allocation fails
In the Linux kernel, the following vulnerability has been resolved:
nvmet-tcp: fix kernel crash if commands allocation fails
If the commands allocation fails in nvmettcpalloccmds() the kernel crashes in nvmettcpreleasequeuework() because of a NULL pointer dereference.
nvmet: failed to install queue 0 cntlid 1 ret 6 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008
Fix the bug by setting queue->nrcmds to zero in case nvmettcpalloccmd() fails.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Configuration
In nvmet_tcp_alloc_cmds(), if commands allocation fails, set queue->nr_cmds to 0 to avoid the NULL pointer dereference in nvmet_tcp_release_queue_work().
Linux kernel nvmet-tcp queue->nr_cmds = 0
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46737?
CVE-2024-46737 has been classified as a high-severity vulnerability due to its potential to cause kernel crashes.
How do I fix CVE-2024-46737?
To fix CVE-2024-46737, update your Linux kernel to a version that is higher than the affected versions such as 5.10.226, 6.1.123, or any later stable release.
What versions of the Linux kernel are affected by CVE-2024-46737?
CVE-2024-46737 affects Linux kernel versions between 5.0 and 5.4.284, 5.5 and 5.10.226, 5.11 and 5.15.167, 5.16 and 6.1.110, 6.2 and 6.6.51, as well as 6.7 and 6.10.10.
What is the impact of CVE-2024-46737?
The impact of CVE-2024-46737 is a potential kernel crash resulting from a NULL pointer dereference during command allocation failure.
Is there any known workaround for CVE-2024-46737?
There are currently no specific workarounds documented for CVE-2024-46737, so applying the recommended updates is advisable.