Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected dc55e35f9e810f23dd69cfdc91a3d636023f57a2 – < 4dd36cf72d2c6c090958c0d7b542fa8211635d2d
    • affected dc55e35f9e810f23dd69cfdc91a3d636023f57a2 – < 4aef6ceb4d6acacd53bc047ac4849677c3edbec1
    • affected dc55e35f9e810f23dd69cfdc91a3d636023f57a2 – < c0620b648321fff654173d238d4a85298ea16d05
    • affected dc55e35f9e810f23dd69cfdc91a3d636023f57a2 – < f0e48172a59e517e613b73f73cc35f24fd123aeb
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.12.117 – ≤ 6.12.*
    • unaffected 6.18.61 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99172 badge
[![CVE-2026-99172](https://cveledger.app/badge/CVE-2026-99172.svg)](https://cveledger.app/cve/CVE-2026-99172)

Record last updated .