CVE-2026-98646: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-vfmc-fwrh-r2q5
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98646
GHSA Identifier GHSA-vfmc-fwrh-r2q5
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-98646

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-98646, 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: tcp: Skip cond_resched() in inet_csk_listen_stop() under BPF context bpf_sock_destroy() runs from the tcp iterator, under rcu_read_lock(). If the sock is a listener that still has children in its accept queue, tcp_abort() ends up in inet_csk_listen_stop() and the cond_resched() there trips the debug check: BUG: sleeping function called from invalid context at net/ipv4/inet_connection_sock.c:1523 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 628, name: test_progs preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 locks held by test_progs/628: 3, last CPU#3: #0: ffff8881158cee18 (&p->lock){+.+.}-{4:4}, at: bpf_seq_read+0x56/0x1210 #1: ffff8881106bb858 (sk_lock-AF_INET6){+.+.}-{0:0}, at: bpf_iter_tcp_seq_show+0x32b/0x4b0 #2: ffffffffb435af20 (rcu_read_lock){....}-{1:3}, at: bpf_iter_run_prog+0x46b/0xde0 CPU: 3 UID: 0 PID: 628 Comm: test_progs Tainted: G W 7.2.0+ #65 PREEMPT Tainted: [W]=WARN Call Trace: <TASK> dump_stack_lvl+0xc1/0xf0 dump_stack+0x10/0x20 __might_resched+0x3d2/0x610 inet_csk_listen_stop+0x7b/0xbf0 tcp_abort+0x23b/0x3b0 bpf_sock_destroy+0xfc/0x140 bpf_prog_448133d24601754f_iter_tcp6_server+0x81/0x8a bpf_iter_run_prog+0x538/0xde0 bpf_iter_tcp_seq_show+0x26b/0x4b0 bpf_seq_read+0x424/0x1210 vfs_read+0x197/0xe40 ksys_read+0x119/0x240 __x64_sys_read+0x72/0xc0 x64_sys_call+0x647/0x27e0 do_syscall_64+0xe5/0x610 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fad39b28aca RSP: 002b:00007ffc381c61c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00007ffc381c6a88 RCX: 00007fad39b28aca RDX: 0000000000000032 RSI: 00007ffc381c6250 RDI: 0000000000000014 RBP: 00007ffc381c61e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003 R13: 0000000000000000 R14: 000055f077c1bbb0 R15: 00007fad3a0f3000 </TASK> The commit that added the kfunc already guards lock_sock() in tcp_abort() and udp_abort() with has_current_bpf_ctx(), but missed the listener path. Do the same for the cond_resched(). The loop runs inside the iterator's rcu_read_lock(), it must not reschedule or report a quiescent state there.

References

NVD — CVE-2026-98646 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98646
git.kernel.org/stable/c/23da88d159... WEB
https://git.kernel.org/stable/c/23da88d1597ee7fdda373e1530284b763710911f
git.kernel.org/stable/c/55bbebf282... WEB
https://git.kernel.org/stable/c/55bbebf2829c3f47c5a48fc261740301d0f25f48
git.kernel.org/stable/c/5b52417c61... WEB
https://git.kernel.org/stable/c/5b52417c6196e05618a3b5d9753dbed9adef0166
git.kernel.org/stable/c/eaab8cab45... WEB
https://git.kernel.org/stable/c/eaab8cab451b9502ce224cd202550375b894a467
git.kernel.org/stable/c/ee7246bccb... WEB
https://git.kernel.org/stable/c/ee7246bccb9da66076dd8094daa48bdc761d6b76

Frequently Asked Questions

What is CVE-2026-98646?
CVE-2026-98646 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-98646?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98646?
CVE-2026-98646 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98646?
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-vfmc-fwrh-r2q5",
  "modified" : "2026-10-18T18:31:58Z",
  "published" : "2026-10-18T18:31:57Z",
  "aliases" : [ "CVE-2026-98646" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntcp: Skip cond_resched() in inet_csk_listen_stop() under BPF context\n\nbpf_sock_destroy() runs from the tcp iterator, under rcu_read_lock(). If\nthe sock is a listener that still has children in its accept queue,\ntcp_abort() ends up in inet_csk_listen_stop() and the cond_resched()\nthere trips the debug check:\n\nBUG: sleeping function called from invalid context at net/ipv4/inet_connection_sock.c:1523\nin_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 628, name: test_progs\npreempt_count: 0, expected: 0\nRCU nest depth: 1, expected: 0\nlocks held by test_progs/628: 3, last CPU#3:\n #0: ffff8881158cee18 (&p->lock){+.+.}-{4:4}, at: bpf_seq_read+0x56/0x1210\n #1: ffff8881106bb858 (sk_lock-AF_INET6){+.+.}-{0:0}, at: bpf_iter_tcp_seq_show+0x32b/0x4b0\n #2: ffffffffb435af20 (rcu_read_lock){....}-{1:3}, at: bpf_iter_run_prog+0x46b/0xde0\nCPU: 3 UID: 0 PID: 628 Comm: test_progs Tainted: G        W           7.2.0+ #65 PREEMPT\nTainted: [W]=WARN\nCall Trace:\n <TASK>\n dump_stack_lvl+0xc1/0xf0\n dump_stack+0x10/0x20\n __might_resched+0x3d2/0x610\n inet_csk_listen_stop+0x7b/0xbf0\n tcp_abort+0x23b/0x3b0\n bpf_sock_destroy+0xfc/0x140\n bpf_prog_448133d24601754f_iter_tcp6_server+0x81/0x8a\n bpf_iter_run_prog+0x538/0xde0\n bpf_iter_tcp_seq_show+0x26b/0x4b0\n bpf_seq_read+0x424/0x1210\n vfs_read+0x197/0xe40\n ksys_read+0x119/0x240\n __x64_sys_read+0x72/0xc0\n x64_sys_call+0x647/0x27e0\n do_syscall_64+0xe5/0x610\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fad39b28aca\nRSP: 002b:00007ffc381c61c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000000\nRAX: ffffffffffffffda RBX: 00007ffc381c6a88 RCX: 00007fad39b28aca\nRDX: 0000000000000032 RSI: 00007ffc381c6250 RDI: 0000000000000014\nRBP: 00007ffc381c61e0 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000003\nR13: 0000000000000000 R14: 000055f077c1bbb0 R15: 00007fad3a0f3000\n </TASK>\n\nThe commit that added the kfunc already guards lock_sock() in tcp_abort()\nand udp_abort() with has_current_bpf_ctx(), but missed the listener path.\nDo the same for the cond_resched(). The loop runs inside the iterator's\nrcu_read_lock(), it must not reschedule or report a quiescent state there.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98646"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/23da88d1597ee7fdda373e1530284b763710911f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/55bbebf2829c3f47c5a48fc261740301d0f25f48"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5b52417c6196e05618a3b5d9753dbed9adef0166"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/eaab8cab451b9502ce224cd202550375b894a467"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ee7246bccb9da66076dd8094daa48bdc761d6b76"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:17Z"
  }
}