CVE-2026-99172
ipc: drop the mqueue mount with kern_unmount() on setup failure
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ipc: drop the mqueue mount with kern_unmount() on setup failure
mq_init_ns() creates the mqueue mount with fc_mount_longterm(), so its ->mnt_ns is MNT_NS_INTERNAL. When setting up the mqueue or ipc sysctls or msg_init_ns() fails afterwards, create_ipc_ns() drops it with a plain mntput(). With ->mnt_ns set that takes the fast path of mntput_no_expire(). The count drops to zero and nothing ever kills the mount, so the mount and the mqueue superblock are leaked.
Commit dc55e35f9e81 ("ipc: Store mqueue sysctls in the ipc namespace") added the first failure path after mq_init_ns() and never dropped the mount. Commit 7229d74e5e8c ("ipc: create_ipc_ns: drop mqueue mount on sysctl setup failure") tried to fix that with a mntput() but that doesn't help for a long-term mount.
Use kern_unmount(). free_ipc() open-codes the same thing for a namespace that made it.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: dc55e35f9e810f23dd69cfdc91a3d636023f57a2 to < 4dd36cf72d2c6c090958c0d7b542fa8211635d2d; affected: dc55e35f9e810f23dd69cfdc91a3d636023f57a2 to < 4aef6ceb4d6acacd53bc047ac4849677c3edbec1; affected: dc55e35f9e810f23dd69cfdc91a3d636023f57a2 to < c0620b648321fff654173d238d4a85298ea16d05; affected: dc55e35f9e810f23dd69cfdc91a3d636023f57a2 to < f0e48172a59e517e613b73f73cc35f24fd123aeb | See vendor advisory |
| LinuxLinux | affected: 5.19; unaffected: 0 to < 5.19; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.2.13 to ≤ 7.2.*; unaffected: 7.3 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99172
- https://git.kernel.org/stable/c/4dd36cf72d2c6c090958c0d7b542fa8211635d2d
- https://git.kernel.org/stable/c/4aef6ceb4d6acacd53bc047ac4849677c3edbec1
- https://git.kernel.org/stable/c/c0620b648321fff654173d238d4a85298ea16d05
- https://git.kernel.org/stable/c/f0e48172a59e517e613b73f73cc35f24fd123aeb