CVE-2026-98539: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-fgm8-xgjp-8vhv
Share
Published
Advisory Summary

CVE-2026-98539 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98539 at a Glance

CVE Identifier CVE-2026-98539
GHSA Identifier GHSA-fgm8-xgjp-8vhv
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98539

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98539, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: use d_instantiate_new() in ntfs_create_inode() and murder syzbot's "WARNING in do_new_mount" saga ntfs_create_inode() creates a new inode via ntfs_new_inode(). It hashes it with insert_inode_locked() and so it's marked as I_NEW until unlock_new_inode(). ntfs 3 calls d_instantiate() in between though... Since the dentry was already hashed by the lookup before the create any path walk finds it without touching the parent's i_rwsem and so can lock the inode. If the inode is a directory unlock_new_inode() calls lockdep_annotate_inode_mutex_key() and marks i_rwsem with the i_mutex_dir_key class. That resets the count and the owner of a lock somebody else may already hold by now... syzbot has been spamming us with the same godforsaken bug "WARNING in do_new_mount" since 2023. I can't take it anymore so I went looking. Afaict, syzbot's executor chdirs into a freshly mounted ntfs3 image, creates a directory and then mounts some pseudofs on it. Everytime the mkdir() takes longer than syzbot waits mount() runs concurrently: mkdir("./sys") mount(NULL, "./sys", "sysfs") ntfs_create_inode() d_instantiate() user_path_at() finds the dentry do_lock_mount() inode_lock(inode) namespace_lock() unlock_new_inode() lockdep_annotate_inode_mutex_key() init_rwsem(&inode->i_rwsem) unlock_mount() inode_unlock(inode) The mount side then releases a lock that according to the rwsem nobody holds: DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && ...): count = 0x0, magic = 0xffff888043a854e8, owner = 0x0, curr 0xffff888000244880, list empty WARNING: CPU: 0 PID: 5346 at kernel/locking/rwsem.c:1368 __up_write Call Trace: inode_unlock include/linux/fs.h:877 [inline] unlock_mount fs/namespace.c:2892 [inline] do_new_mount_fc fs/namespace.c:3828 [inline] do_new_mount+0x777/0xa40 fs/namespace.c:3887 On PREEMPT_RT the same thing shows up as DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current) WARNING: kernel/locking/rtmutex_common.h:193 at rt_mutex_slowunlock The up_write() underflows the reset count. A following inode_lock() on that directory then never returns. A path walk into the new directory racing with the mkdir() corrupts the lock the same way via inode_lock_shared() in lookup_slow(). Switch to d_instantiate_new() and drop the trailing unlock_new_inode(). All error paths bail out before that point with I_NEW still set and keep using discard_new_inode(). May we never see this fscking bug report again.

References

NVD — CVE-2026-98539 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98539
git.kernel.org/stable/c/1abd643f37... WEB
https://git.kernel.org/stable/c/1abd643f3783ea8f8e273c18697ff0413aa92dc7
git.kernel.org/stable/c/1ae2a242c1... WEB
https://git.kernel.org/stable/c/1ae2a242c15b03470b1b16289298e597bbe3bb29
git.kernel.org/stable/c/37ec7353f4... WEB
https://git.kernel.org/stable/c/37ec7353f4ac495b28284b0fcb0e53d21d1b3f3f
git.kernel.org/stable/c/6fda7121cb... WEB
https://git.kernel.org/stable/c/6fda7121cb6a8ea6fbd77d0f787f04b8e8b5358e

Frequently Asked Questions

What is CVE-2026-98539?
CVE-2026-98539 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98539?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98539?
CVE-2026-98539 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98539?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fgm8-xgjp-8vhv",
  "modified" : "2026-10-18T18:31:53Z",
  "published" : "2026-10-18T18:31:53Z",
  "aliases" : [ "CVE-2026-98539" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: use d_instantiate_new() in ntfs_create_inode() and murder syzbot's \"WARNING in do_new_mount\" saga\n\nntfs_create_inode() creates a new inode via ntfs_new_inode(). It hashes\nit with insert_inode_locked() and so it's marked as I_NEW until\nunlock_new_inode().\n\nntfs 3 calls d_instantiate() in between though... Since the dentry was\nalready hashed by the lookup before the create any path walk finds it\nwithout touching the parent's i_rwsem and so can lock the inode.\n\nIf the inode is a directory unlock_new_inode() calls\nlockdep_annotate_inode_mutex_key() and marks i_rwsem with the\ni_mutex_dir_key class.\n\nThat resets the count and the owner of a lock somebody else may already\nhold by now...\n\nsyzbot has been spamming us with the same godforsaken bug\n\n  \"WARNING in do_new_mount\"\n\nsince 2023. I can't take it anymore so I went looking. Afaict, syzbot's\nexecutor chdirs into a freshly mounted ntfs3 image, creates a\ndirectory and then mounts some pseudofs on it. Everytime the mkdir()\ntakes longer than syzbot waits mount() runs concurrently:\n\n  mkdir(\"./sys\")                        mount(NULL, \"./sys\", \"sysfs\")\n  ntfs_create_inode()\n    d_instantiate()\n                                        user_path_at() finds the dentry\n                                        do_lock_mount()\n                                          inode_lock(inode)\n                                          namespace_lock()\n    unlock_new_inode()\n      lockdep_annotate_inode_mutex_key()\n        init_rwsem(&inode->i_rwsem)\n                                        unlock_mount()\n                                          inode_unlock(inode)\n\nThe mount side then releases a lock that according to the rwsem nobody\nholds:\n\n  DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && ...):\n  count = 0x0, magic = 0xffff888043a854e8, owner = 0x0,\n  curr 0xffff888000244880, list empty\n  WARNING: CPU: 0 PID: 5346 at kernel/locking/rwsem.c:1368 __up_write\n  Call Trace:\n   inode_unlock include/linux/fs.h:877 [inline]\n   unlock_mount fs/namespace.c:2892 [inline]\n   do_new_mount_fc fs/namespace.c:3828 [inline]\n   do_new_mount+0x777/0xa40 fs/namespace.c:3887\n\nOn PREEMPT_RT the same thing shows up as\n\n  DEBUG_LOCKS_WARN_ON(rt_mutex_owner(lock) != current)\n  WARNING: kernel/locking/rtmutex_common.h:193 at rt_mutex_slowunlock\n\nThe up_write() underflows the reset count. A following inode_lock() on\nthat directory then never returns. A path walk into the new directory\nracing with the mkdir() corrupts the lock the same way via\ninode_lock_shared() in lookup_slow().\n\nSwitch to d_instantiate_new() and drop the trailing unlock_new_inode().\nAll error paths bail out before that point with I_NEW still set and\nkeep using discard_new_inode().\n\nMay we never see this fscking bug report again.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98539"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1abd643f3783ea8f8e273c18697ff0413aa92dc7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1ae2a242c15b03470b1b16289298e597bbe3bb29"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37ec7353f4ac495b28284b0fcb0e53d21d1b3f3f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6fda7121cb6a8ea6fbd77d0f787f04b8e8b5358e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:05Z"
  }
}