VulnerabilityPublished 28 Oct 2026

CVE-2026-99172: Linux kernel · ipc: drop the mqueue mount with kern_unmount() on setup failure

Source GCVE Database

Authoritative record:CVE-2026-99172

Not known to be exploited : upgrade to f0e48172a59e517e613b73f73cc35f24fd123aeb or c0620b648321fff654173d238d4a85298ea16d05 when convenient.

Data as of 28 Oct 2026, 13:57 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in f0e48172a59e517e613b73f73cc35f24fd123aeb, c0620b648321fff654173d238d4a85298ea16d05

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-c64w-44gc-4h7w

What to do

Upgrade Linux kernel to f0e48172a59e517e613b73f73cc35f24fd123aeb or c0620b648321fff654173d238d4a85298ea16d05.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ dc55e35f9e810f23dd69cfdc91a3d636023f57a2, < f0e48172a59e517e613b73f73cc35f24fd123aeb	Fixed in f0e48172a59e517e613b73f73cc35f24fd123aeb
LinuxLinux	Affected ≥ dc55e35f9e810f23dd69cfdc91a3d636023f57a2, < c0620b648321fff654173d238d4a85298ea16d05	Fixed in c0620b648321fff654173d238d4a85298ea16d05
LinuxLinux	Affected =5.19	Fixed in–

AI-suggested

A fix is available that replaces the improper mntput() call with kern_unmount() to correctly drop the mqueue mount on setup failure. Users should apply the official Linux kernel patches that include this fix. Since this is a kernel-level issue, updating to a fixed kernel version is the recommended remediation.

Description

A vulnerability in the Linux kernel's IPC subsystem involves improper cleanup of the mqueue mount on setup failure, leading to resource leakage. Specifically, when setting up mqueue or IPC sysctls fails after the mqueue mount is created, the mount is not properly dropped, causing the mount and mqueue superblock to leak.

References

Community reviews

Loading reviews…