CVE-2026-98644: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-p6rx-8wrq-4gc7
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98644
GHSA Identifier GHSA-p6rx-8wrq-4gc7
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-98644

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-98644, 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: bpf: Avoid soft lockup in __htab_map_lookup_and_delete_batch() __htab_map_lookup_and_delete_batch() has no rescheduling point. The batch count bounds how many entries are copied out, not how many buckets are visited, so one BPF_MAP_LOOKUP_BATCH call can walk the map end to end. The empty-bucket fast path is worse: it stays inside a single rcu_read_lock() / bpf_disable_instrumentation() section for any run of consecutive empty buckets. That holds up on small maps, but it falls apart at scale. On a 144-CPU arm64 host running a CONFIG_PREEMPT_NONE kernel, periodic BPF_MAP_LOOKUP_BATCH calls against an LRU hash map with 16,777,216 buckets held a CPU inside the batch op for 77+ seconds and triggered the soft lockup watchdog. Commit 75134f16e7dd ("bpf: Add schedule points in batch ops") fixed this same problem in the generic batch ops, but not in this htab-native path, which every htab-based hash map variant uses for its lookup[_and_delete] batch ops. Complete that fix here. Leave the critical section after 64 consecutive empty buckets, call cond_resched_tasks_rcu_qs(), and resume at the saved bucket cursor. No locks are held at that point, and resuming from the cursor is already the function's behavior for non-empty buckets. Add the same call to the per-bucket loop after copy_to_user(), where every lock has been dropped. cond_resched_rcu() is not enough here: sleeping with bpf_prog_active elevated makes tracing programs on that CPU silently skip their invocations. Plain cond_resched() is not enough either. It is a no-op under PREEMPT and PREEMPT_LAZY, the only models arm64 and x86 have offered since commit 7dadeaa6e851 ("sched: Further restrict the preemption modes"). It is also never a Tasks RCU quiescent state, in any model: the reschedule counts as a preemption. The walking task stays a holdout and stalls every synchronize_rcu_tasks() caller, ftrace and BPF trampoline teardown included, until the syscall returns [1]. cond_resched_tasks_rcu_qs() is the usual tool for that [2]. It reports the quiescent state at each yield and still reschedules as cond_resched() does on PREEMPT_NONE and PREEMPT_VOLUNTARY kernels.

References

NVD — CVE-2026-98644 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98644
git.kernel.org/stable/c/44f9bcb5ab... WEB
https://git.kernel.org/stable/c/44f9bcb5ab2b268bc763ed3ebec83308b4972936
git.kernel.org/stable/c/4e48fe9b1c... WEB
https://git.kernel.org/stable/c/4e48fe9b1c77966bede0a73feb3059d7595f642d
git.kernel.org/stable/c/5c8b1869cb... WEB
https://git.kernel.org/stable/c/5c8b1869cb99a32a962388848cd19604fb41263e
git.kernel.org/stable/c/77a3b52b44... WEB
https://git.kernel.org/stable/c/77a3b52b4455e6377e549539e757bc55eedefb51
git.kernel.org/stable/c/85136bf224... WEB
https://git.kernel.org/stable/c/85136bf22404474a815fc0ed26ec0d1cbc1bc3f9
git.kernel.org/stable/c/ca5bd55fc5... WEB
https://git.kernel.org/stable/c/ca5bd55fc508fbb5c08c62206d02237a5b6fc7e8
git.kernel.org/stable/c/f0c09de08e... WEB
https://git.kernel.org/stable/c/f0c09de08ec077098b7e1563f2285f1c136cd816

Frequently Asked Questions

What is CVE-2026-98644?
CVE-2026-98644 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-98644?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98644?
CVE-2026-98644 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98644?
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-p6rx-8wrq-4gc7",
  "modified" : "2026-10-18T18:31:57Z",
  "published" : "2026-10-18T18:31:57Z",
  "aliases" : [ "CVE-2026-98644" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Avoid soft lockup in __htab_map_lookup_and_delete_batch()\n\n__htab_map_lookup_and_delete_batch() has no rescheduling point. The\nbatch count bounds how many entries are copied out, not how many\nbuckets are visited, so one BPF_MAP_LOOKUP_BATCH call can walk the\nmap end to end. The empty-bucket fast path is worse: it stays inside\na single rcu_read_lock() / bpf_disable_instrumentation() section for\nany run of consecutive empty buckets.\n\nThat holds up on small maps, but it falls apart at scale. On a\n144-CPU arm64 host running a CONFIG_PREEMPT_NONE kernel, periodic\nBPF_MAP_LOOKUP_BATCH calls against an LRU hash map with 16,777,216\nbuckets held a CPU inside the batch op for 77+ seconds and triggered\nthe soft lockup watchdog.\n\nCommit 75134f16e7dd (\"bpf: Add schedule points in batch ops\") fixed this\nsame problem in the generic batch ops, but not in this htab-native path,\nwhich every htab-based hash map variant uses for its lookup[_and_delete]\nbatch ops.\n\nComplete that fix here. Leave the critical section after 64 consecutive\nempty buckets, call cond_resched_tasks_rcu_qs(), and resume at the saved\nbucket cursor. No locks are held at that point, and resuming from the\ncursor is already the function's behavior for non-empty buckets. Add the\nsame call to the per-bucket loop after copy_to_user(), where every lock\nhas been dropped. cond_resched_rcu() is not enough here: sleeping with\nbpf_prog_active elevated makes tracing programs on that CPU silently\nskip their invocations.\n\nPlain cond_resched() is not enough either. It is a no-op under PREEMPT\nand PREEMPT_LAZY, the only models arm64 and x86 have offered since\ncommit 7dadeaa6e851 (\"sched: Further restrict the preemption modes\").\nIt is also never a Tasks RCU quiescent state, in any model: the\nreschedule counts as a preemption. The walking task stays a holdout and\nstalls every synchronize_rcu_tasks() caller, ftrace and BPF trampoline\nteardown included, until the syscall returns [1].\ncond_resched_tasks_rcu_qs() is the usual tool for that [2]. It reports\nthe quiescent state at each yield and still reschedules as\ncond_resched() does on PREEMPT_NONE and PREEMPT_VOLUNTARY kernels.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98644"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/44f9bcb5ab2b268bc763ed3ebec83308b4972936"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4e48fe9b1c77966bede0a73feb3059d7595f642d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5c8b1869cb99a32a962388848cd19604fb41263e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77a3b52b4455e6377e549539e757bc55eedefb51"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/85136bf22404474a815fc0ed26ec0d1cbc1bc3f9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ca5bd55fc508fbb5c08c62206d02237a5b6fc7e8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f0c09de08ec077098b7e1563f2285f1c136cd816"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:17Z"
  }
}