CVE-2024-53175: Linux kernel · ipc: fix memleak if msg_init_ns failed in create_ipc_ns
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1027.29~22.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 11:13 UTC
- Patch
- Available – fixed in 6.8.0-1027.29~22.04.1, 6.8.0-1027.32~22.04.1, 6.8.0-1028.30~22.04.1 +29
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7450-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7451-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7452-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7453-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7468-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: ipc: fix memleak if msg_init_ns failed in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size 512): comm "shmem_2nstest", pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........ .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420 [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0 [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920 [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0 [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0 [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53
References
- ubuntu.com/security/CVE-2024-53175 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-53175 (opens in a new tab)
- git.kernel.org/linus/bc8f5921cd69188627c08041276238de222ab466 (opens in a new tab)
- git.kernel.org/stable/c/10209665b5bf199f8065b2e7d2b2dc6cdf227117 (opens in a new tab)
- git.kernel.org/stable/c/3d230cfd4b9b0558c7b2039ba1def2ce6b6cd158 (opens in a new tab)
- git.kernel.org/stable/c/8fed302872e26c7bf44d855c53a1cde747172d58 (opens in a new tab)
- git.kernel.org/stable/c/928de5fcd462498b8334107035da8ab85e316d8a (opens in a new tab)
- git.kernel.org/stable/c/bc8f5921cd69188627c08041276238de222ab466 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7450-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7451-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7452-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7453-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7449-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7468-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7523-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7524-1 (opens in a new tab)