Answer in brief
CVE-2026-98984 records a Unknown severity vulnerability in dcache: don't put a mountpoint on a dentry that's being removed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1064f874abc0d05eeed8993815f584d847b72486 <5e6bfd9f249f2c74bb63c0f06ad959da3bee0971 || >=1064f874abc0d05eeed8993815f584d847b72486 <793cb67b0f52d00c67bd0e76bc57455b5c70ebb8 || >=1064f874abc0d05eeed8993815f584d847b72486 <390ddcea2a8aca411b931a8e2863a80ccca8d2b3 || >=1064f874abc0d05eeed8993815f584d847b72486 <30a1625022411a387cce9239408ece9955bc9c58 || >=1064f874abc0d05eeed8993815f584d847b72486 <75f4197f1e11d2eb75c2d6f916a7d4764db621e5 || 5e6ef5ef6eaf690faad3a7c6c665ebf45d7b6ccf || 839d42687dfce0ed0ea2c6bd8d707cc0e276fbe7 || 808e83e5add13152bd4a88346487de68395c136b || 6de9d08a9718ee9c12ba6343c50141c2d633e3dc || >=4.1.40 <4.2 || >=4.4.54 <4.5 || >=4.9.15 <4.10 || >=4.10.3 <4.11 | 5e6bfd9f249f2c74bb63c0f06ad959da3bee0971, 793cb67b0f52d00c67bd0e76bc57455b5c70ebb8, 390ddcea2a8aca411b931a8e2863a80ccca8d2b3, 30a1625022411a387cce9239408ece9955bc9c58, 75f4197f1e11d2eb75c2d6f916a7d4764db621e5, 4.2, 4.5, 4.10, 4.11 |
| Linux/Linuxgeneric | 4.11 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
In the Linux kernel, the following vulnerability has been resolved: dcache: don't put a mountpoint on a dentry that's being removed rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts(). But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed: rmrace: b passed dont_mount() and detach_mounts(), sleeping T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 () T1: rmdir(/tmp/plcant/d/b) = 0 errno 0 109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw 108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it. Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.
Quoted source text, attributed separately from HOL analysis.