CVE-2026-99172

ipc: drop the mqueue mount with kern_unmount() on setup failure

Published Oct 28, 2026 CVSS 3.1 · 2.5 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

In the Linux kernel, the process that creates message queue mounts within the IPC namespace cleans up the mount only when a plain reference count decrement is applied. When IPC sysctl parameter or message queue initialization fails, the mount is left attached. The mount and its superblock survive, causing a persistent leak of kernel memory and mount table entries. Over time, repeated failures can exhaust mount resources or memory, which may lead to kernel instability or a denial of service. This flaw is an instance of improper resource cleanup (CWE-772).

Affected Systems

This defect exists in Linux kernel releases that contain the original IPC namespace setup code for mqueue mounts but have not incorporated the corrective logic that prevents the leak. The advisory does not list exact kernel versions, so any kernel derived from the before the successful fix commit is considered vulnerable. Administrators should verify whether their kernel branch includes the fix by checking the repository history or consulting the vendor’s patch notes.

Risk and Exploitability

The vulnerability carries a CVSS score of 2.5 and an EPSS score below 1 %, and it is not listed in the CISA KEV catalog. While the CVE description does not explicitly state the required access level, it is inferred that local or privileged access is needed to trigger the failure during IPC sysctl or message queue creation; the path is therefore limited to systems where such operations are possible. While no widespread exploitation is documented, the accumulation of leaked mounts can degrade system resources gradually, potentially allowing a local attacker to force a denial of service over time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the operating system to a kernel version that incorporates the patch correcting the mqueue mount cleanup logic.
  • If a kernel upgrade cannot be performed immediately, limit or audit operations that modify IPC sysctl parameters or create message queues to avoid triggering the failure path.
  • Continuously monitor the mount table (e.g., via /proc/self/mountinfo) for orphaned mqueue mounts and reboot or restart affected services when an abnormal number of mounts is detected.

Generated by OpenCVE AI on October 29, 2026 at 18:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-401
CWE-404
Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

cvssV3_1

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Low

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-401
CWE-404
Type Values Removed Values Added
Description 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.
Title ipc: drop the mqueue mount with kern_unmount() on setup failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 10, 2026, 6:15 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Nov 10, 2026, 7:22 PM
Severity
Low
Public date
Oct 28, 2026, 12:00 AM