ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-98995

In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of th

Published Oct 23, 2026 · catalog updated Oct 25, 2026 · In the Linux kernel,

Last checked Nov 3, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-98995. EPSS is 0.16%. Act only if a listed version of In the Linux kernel, is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (In the Linux kernel,).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.16%
Remediation
Advisory link
Affected products
Debian:14 linux

In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it. For a mount that is moved beneath in attach_recursive_mnt() that doesn't matter. The new mount has already reset ->overmount of the old parent by the time the old top mount is moved onto it. It matters for reparent() though. propagate_umount() moves a surviving overmount onto the first ancestor that isn't going to be unmounted. The mount it was taken from is unmounted immediately afterwards. If a file descriptor keeps that unmounted mount alive ->overmount points at the moved mount. That's a dangling pointer and UAF as the moved mount is unmounted and freed. do_lock_mount() follows ->overmount from the target path under mount_lock. With a file descriptor on such a mount as the target of a mount beneath topmost_overmount() walks into the freed mount and do_lock_mount() takes references on whatever it finds there. So reset ->overmount of the old parent in mnt_change_mountpoint() the same way __umount_mnt() does. A mount's ->overmount is then always a mount that is attached to it.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:14 linux0 → 7.2.11-1

How to fix CVE-2026-98995

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-98995. EPSS is 0.16%. Act only if a listed version of In the Linux kernel, is installed.

Which versions are affected?

Compare what you have installed with 0 → 7.2.11-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.16%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · Tenable CVE Database

    Detected

    In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it. For a mount that is moved beneath in attach_recursive_m

  2. Oct 25, 2026 · Trivy Vulnerability DB

    Fix available

    linux fixed in 7.2.11-1

  3. Oct 25, 2026 · Trivy Vulnerability DB

    Fix available

    linux fixed in 7.2.11-1

  4. Oct 25, 2026 · Trivy Vulnerability DB

    Updated

    In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it. For a mount that is moved beneath in attach_recursive_m

Sources

  • CVE.orgVulnerability recordCVE-2026-98995

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-98995

    30-day exploitation probability 0.16%

    first.org
  • OpenCVEVendor advisoryCVE-2026-98995

    CVE-2026-98995 is named on the public OpenCVE page.

    opencve.io
  • Tenable CVE DatabaseVulnerability recordCVE-2026-98995

    In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it. For a mount that is moved beneath in attach_recursive_m

    tenable.com
  • Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-98995

    In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's ->overmount in mnt_change_mountpoint() __umount_mnt() resets ->overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves th

    osv.dev

References

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 28, 2026
  • Trivy Vulnerability DBOct 25, 2026
  • Tenable CVE DatabaseOct 25, 2026
  • OpenCVEOct 24, 2026
  • CVE.orgOct 23, 2026