CVE-2026-98829: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98829 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-98829 at a Glance
How to Fix CVE-2026-98829
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.
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-98829, 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
References
Frequently Asked Questions
What is CVE-2026-98829?
Which Software versions are affected?
What version fixes CVE-2026-98829?
What CWE is associated with CVE-2026-98829?
How can I check Maven dependencies for CVE-2026-98829?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8w97-qwf2-rgh5",
"modified" : "2026-10-18T18:32:04Z",
"published" : "2026-10-18T18:32:04Z",
"aliases" : [ "CVE-2026-98829" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: drop oversized fragments to avoid extra_len overflow\n\nIn ieee80211_rx_h_defragment(), fragment payloads are accumulated into\nentry->extra_len as subsequent fragments arrive:\n\n entry->extra_len += rx->skb->len;\n\nWhen the final fragment arrives, the head fragment is dequeued, and\npskb_expand_head() is called with entry->extra_len to ensure sufficient\ntailroom for all queued fragments before copying:\n\n if (skb_tailroom(rx->skb) < entry->extra_len) {\n if (unlikely(pskb_expand_head(rx->skb, 0, entry->extra_len,\n GFP_ATOMIC))) {\n ...\n }\n }\n while ((skb = __skb_dequeue(&entry->skb_list))) {\n skb_put_data(rx->skb, skb->data, skb->len);\n dev_kfree_skb(skb);\n }\n\nIn commit 69f132236827 (\"mac80211: shrink struct\nieee80211_fragment_entry\"), entry->extra_len was narrowed from unsigned\nint to u16 in order to reduce structure memory footprint.\n\nHowever, an IEEE 802.11 frame sequence can contain up to 16 fragments\n(frag numbers 0..15). If a sequence of large fragments arrives (e.g. from\na malicious peer or rogue AP), the sum of fragment lengths can exceed\n65535 bytes (for example, 15 fragments of 4400 bytes total 66000 bytes).\nBecause extra_len is a u16, this addition overflows and wraps around\nmodulo 65536 (e.g. 66000 wraps to 464).\n\nConsequently, pskb_expand_head() allocates only the truncated amount of\ntailroom (or is skipped entirely if the head fragment already has >= 464\nbytes of tailroom). When skb_put_data() subsequently iterates through the\nqueued skb list, it appends the full payload into the undersized buffer,\ncausing skb_put() to trigger skb_over_panic() and crash the kernel in\nsoftirq context.\n\nA legitimate MSDU in IEEE 802.11 is at most 2304 bytes (or up to 7935/11454\nbytes for A-MSDU, which is not fragmented), well below U16_MAX.\n\nFix this without increasing the size of struct ieee80211_fragment_entry by\nchecking whether adding the incoming fragment length would exceed U16_MAX.\nIf so, purge the queued fragments and drop the frame.\n\n[assign a separate drop reason]",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98829"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5e4f3509793b4db2c0835340224743db680e861f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/870b8cb9baa9bd859deceb33ae158011e6ba2360"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/9338b2dea74cb0fc80a4c958b68e687610ba2261"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:37Z"
}
}