CVE-2024-53118: vsock: Fix sk_error_queue memory leak
In the Linux kernel, the following vulnerability has been resolved:
vsock: Fix skerrorqueue memory leak
Kernel queues MSGZEROCOPY completion notifications on the error queue. Where they remain, until explicitly recv()ed. To prevent memory leaks, clean up the queue when the socket is destroyed.
unreferenced object 0xffff8881028beb00 (size 224): comm "vsocktest", pid 1218, jiffies 4294694897 hex dump (first 32 bytes): 90 b0 21 17 81 88 ff ff 90 b0 21 17 81 88 ff ff ..!.......!..... 00 00 00 00 00 00 00 00 00 b0 21 17 81 88 ff ff ..........!..... backtrace (crc 6c7031ca): [<ffffffff81418ef7>] kmemcacheallocnodenoprof+0x2f7/0x370 [<ffffffff81d35882>] allocskb+0x132/0x180 [<ffffffff81d2d32b>] sockomalloc+0x4b/0x80 [<ffffffff81d3a8ae>] msgzerocopyrealloc+0x9e/0x240 [<ffffffff81fe5cb2>] virtiotransportsendpktinfo+0x412/0x4c0 [<ffffffff81fe6183>] virtiotransportstreamenqueue+0x43/0x50 [<ffffffff81fe0813>] vsockconnectiblesendmsg+0x373/0x450 [<ffffffff81d233d5>] syssendmsg+0x365/0x3a0 [<ffffffff81d246f4>] syssendmsg+0x84/0xd0 [<ffffffff81d26f47>] syssendmsg+0x47/0x80 [<ffffffff820d3df3>] dosyscall64+0x93/0x180 [<ffffffff8220012b>] entrySYSCALL64afterhwframe+0x76/0x7e
Other sources
In the Linux kernel, the following vulnerability has been resolved:
vsock: Fix skerrorqueue memory leak
Kernel queues MSGZEROCOPY completion notifications on the error queue. Where they remain, until explicitly recv()ed. To prevent memory leaks, clean up the queue when the socket is destroyed.
unreferenced object 0xffff8881028beb00 (size 224): comm "vsocktest", pid 1218, jiffies 4294694897 hex dump (first 32 bytes): 90 b0 21 17 81 88 ff ff 90 b0 21 17 81 88 ff ff ..!.......!..... 00 00 00 00 00 00 00 00 00 b0 21 17 81 88 ff ff ..........!..... backtrace (crc 6c7031ca): [<ffffffff81418ef7>] kmemcacheallocnodenoprof+0x2f7/0x370 [<ffffffff81d35882>] allocskb+0x132/0x180 [<ffffffff81d2d32b>] sockomalloc+0x4b/0x80 [<ffffffff81d3a8ae>] msgzerocopyrealloc+0x9e/0x240 [<ffffffff81fe5cb2>] virtiotransportsendpktinfo+0x412/0x4c0 [<ffffffff81fe6183>] virtiotransportstreamenqueue+0x43/0x50 [<ffffffff81fe0813>] vsockconnectiblesendmsg+0x373/0x450 [<ffffffff81d233d5>] syssendmsg+0x365/0x3a0 [<ffffffff81d246f4>] syssendmsg+0x84/0xd0 [<ffffffff81d26f47>] syssendmsg+0x47/0x80 [<ffffffff820d3df3>] dosyscall64+0x93/0x180 [<ffffffff8220012b>] entrySYSCALL64afterhwframe+0x76/0x7e
— NVD
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
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53118?
CVE-2024-53118 is considered a moderate severity vulnerability due to the potential for memory leaks in the Linux kernel.
What are the affected versions related to CVE-2024-53118?
CVE-2024-53118 affects Linux kernel versions from 6.7 to 6.11.10 and 6.12 release candidates 1 through 7.
How do I fix CVE-2024-53118?
To remediate CVE-2024-53118, update the Linux kernel to a version that includes the fix.
What is the nature of the issue in CVE-2024-53118?
CVE-2024-53118 involves a memory leak in the vsock component of the Linux kernel when handling MSG_ZEROCOPY completion notifications.
Can CVE-2024-53118 lead to service disruptions?
Yes, CVE-2024-53118 can lead to increased memory usage over time, potentially affecting system stability and performance.