GHSA-JC2X-56VJ-85XR
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In the Linux kernel, the following vulnerability has been resolved:
net/sched: ets: clamp quantum in parse and fallback paths
ets_qdisc_change() falls back to psched_mtu() with no floor for bands without an explicit quantum. With a crafted size table qdisc_pkt_len reaches ~2 GiB, so a zero psched_mtu on a headerless device makes the deficit-refill loop spin under the qdisc lock.
Move the floor into ets_quantum_parse() so explicitly configured quanta are also clamped to [256, 1<<20], not just the fallback path.
Conditions to recreate the bug: CONFIG_NET_SCH_ETS=y. Requires CAP_NET_ADMIN (namespace-local via unshare -Urn suffices).
tc qdisc add dev dummy0 root ets bands 3 strict 2 quanta 1 1
{
"affected": [],
"aliases": [
"CVE-2026-98009"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:29Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: ets: clamp quantum in parse and fallback paths\n\nets_qdisc_change() falls back to psched_mtu() with no floor for bands\nwithout an explicit quantum. With a crafted size table qdisc_pkt_len\nreaches ~2 GiB, so a zero psched_mtu on a headerless device makes the\ndeficit-refill loop spin under the qdisc lock.\n\nMove the floor into ets_quantum_parse() so explicitly configured quanta\nare also clamped to [256, 1\u003c\u003c20], not just the fallback path.\n\nConditions to recreate the bug:\n CONFIG_NET_SCH_ETS=y. Requires CAP_NET_ADMIN (namespace-local via\n unshare -Urn suffices).\n\n tc qdisc add dev dummy0 root ets bands 3 strict 2 quanta 1 1",
"id": "GHSA-jc2x-56vj-85xr",
"modified": "2026-09-25T12:31:32Z",
"published": "2026-09-25T12:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98009"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1c38487f46b243bfeefec0c0c86023a3904f2214"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8f80b113dea0bed3c1a31a4224b72775cd9ec52d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/99ae477b892e203a37985ebc56f0063e072f7f4b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/de22c30ec5598aca8797f02082d2ee1358dfa3ff"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.