CVE-2026-98683: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f8wg-49h3-2qvh
Published
Advisory Summary

CVE-2026-98683 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-98683 at a Glance

CVE Identifier CVE-2026-98683
GHSA Identifier GHSA-f8wg-49h3-2qvh
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-98683

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-98683, 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: smb: client: flush dirty data before zeroing a range smb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the page cache over the target range with truncate_pagecache_range() and then issuing FSCTL_SET_ZERO_DATA to the server. Dirty data was only flushed conditionally, when the range reached or extended EOF. For a purely interior zero range that does not reach EOF, no flush happened, so a dirty folio overlapping the range could be written back to the server after the FSCTL and refill the range that was just zeroed with stale data. Fix this by unconditionally flushing and waiting for dirty data in the range before invalidating the page cache and issuing FSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in commit d7d2adcd022b ("smb/client: flush dirty data before punching a hole"); the two paths are structurally identical here. This is observed as generic/363 randomly reading stale data where a zeroed range is expected against Windows Server.

References

Frequently Asked Questions

What is CVE-2026-98683?
CVE-2026-98683 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-98683?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98683?
CVE-2026-98683 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98683?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f8wg-49h3-2qvh",
  "modified" : "2026-10-18T18:31:59Z",
  "published" : "2026-10-18T18:31:59Z",
  "aliases" : [ "CVE-2026-98683" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: flush dirty data before zeroing a range\n\nsmb3_zero_range() emulates FALLOC_FL_ZERO_RANGE by invalidating the\npage cache over the target range with truncate_pagecache_range() and\nthen issuing FSCTL_SET_ZERO_DATA to the server.\n\nDirty data was only flushed conditionally, when the range reached or\nextended EOF.  For a purely interior zero range that does not reach\nEOF, no flush happened, so a dirty folio overlapping the range could\nbe written back to the server after the FSCTL and refill the range\nthat was just zeroed with stale data.\n\nFix this by unconditionally flushing and waiting for dirty data in the\nrange before invalidating the page cache and issuing\nFSCTL_SET_ZERO_DATA, exactly as was done for smb3_punch_hole() in\ncommit d7d2adcd022b (\"smb/client: flush dirty data before punching a\nhole\"); the two paths are structurally identical here.\n\nThis is observed as generic/363 randomly reading stale data where a\nzeroed range is expected against Windows Server.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98683"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8f8d32c1044f70e46e87550e039a15ff20a4b21c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cecf4114069fc19629d284710fd783d56bbca862"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e8ba21c7e6ef3d4cb617858760673877b2e4a2bb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:21Z"
  }
}