CVE-2026-99638 (GCVE-0-2026-99638)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
74e31ca850c1cddeca03503171dd145b6ce293b6 , < 8182ba13500b39d75b66fe9f37e13cb325c4b17e
(git)
Affected: 74e31ca850c1cddeca03503171dd145b6ce293b6 , < 7445eccce376f7adb876c9f466d7d893344af7ce (git) Affected: 74e31ca850c1cddeca03503171dd145b6ce293b6 , < 7327092a678bfcb1bae033acb1be1006a1399e30 (git) Affected: 74e31ca850c1cddeca03503171dd145b6ce293b6 , < f19f2b308beb158d0e6f6eb806ced636e4ebf6ce (git) |
guessed | |
| Linux | Linux |
Affected:
5.1
Unaffected: 0 , < 5.1 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/sched/sch_generic.c",
"net/sched/sch_taprio.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8182ba13500b39d75b66fe9f37e13cb325c4b17e",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "7445eccce376f7adb876c9f466d7d893344af7ce",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "7327092a678bfcb1bae033acb1be1006a1399e30",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "f19f2b308beb158d0e6f6eb806ced636e4ebf6ce",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/sched/sch_generic.c",
"net/sched/sch_taprio.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"lessThan": "5.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "5.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "5.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "5.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "5.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: clamp skb-\u003equeue_mapping before indexing the tx queue\n\nThis issue was caught by Sashiko (nipa). A producer-side path cap is\nalready merged (ea4d4b5dddb5); this patch adds the matching consumer-side\ncaps.\n\nThe issue:\nThe tx queue is picked and capped in netdev_core_pick_tx() before the\n__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an\negress qdisc (not clsact) can then change __sk_buff-\u003equeue_mapping; that\nstore is never re-checked. bpf_convert_ctx_access() bounds it only by\nNO_QUEUE_MAPPING, not by the device\u0027s queue count.\n\nTwo consumers read the stale value:\n\n - On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which\n indexes dev-\u003e_tx[]. netdev_get_tx_queue() guards it with just a\n DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds\n txq-\u003e_xmit_lock and writes txq-\u003exmit_lock_owner past the end of the\n allocation on non-lltx devices such as ifb. Drivers that index their\n rings from skb_get_queue_mapping() (ex: ifb) go out of range the same\n way.\n\n - On enqueue, taprio_enqueue() indexes q-\u003eqdiscs[] with the same value;\n the array is sized dev-\u003enum_tx_queues. A duplicating netem on a child\n qdisc clones the skb and re-enqueues the clone at the taprio root\n (qdisc_root_bh()) through a direct rootq-\u003eenqueue() call, so the value\n reaches taprio_enqueue() before any dequeue cap runs.\n\nThe Fix:\nCap the mapping at the consumers and write the capped value back, so the\nqdisc\u0027s _tx[] lookup, the taprio q-\u003eqdiscs[] lookup and any later driver\nread stay in range.\n\nOn the dequeue side the cap folds into the dequeue path instead of a\nseparate walk over the returned list: dequeue_skb() caps the head, and\neach bulk helper caps the element it appends. For a qdisc that is not\nTCQ_F_ONETXQUEUE, netdev_cap_txqueue() logs a ratelimited notice and\nselects queue 0.\n\nA TCQ_F_ONETXQUEUE qdisc is bound to a single tx queue: dequeue_skb() uses\nq-\u003edev_queue for the frozen check, the BQL limit and the trace point, while\nqdisc_restart() transmits on the skb\u0027s queue. Capping an out-of-range\nmapping to queue 0 would therefore send a per-queue child\u0027s skb through a\ndifferent queue than the one it was dequeued for. On mq, mqprio, taprio and\nhtb offload children, a stopped queue 0 could then park the list in\nq-\u003egso_skb, and the later wake would schedule queue 0\u0027s own child instead\nof this qdisc. Pin a TCQ_F_ONETXQUEUE mapping to the qdisc\u0027s own queue to\nkeep the documented invariant.\n\nThe pin covers every mapping, not only an out-of-range one: an in-range\nmapping that a filter sets on one of those per-queue children is rewritten\nto the child\u0027s own queue, and this path does not call netdev_cap_txqueue(),\nso it logs no notice. On a single-queue device qdisc_create() sets\nTCQ_F_ONETXQUEUE, so the one-queue trigger described below also takes this\nbranch and is corrected without a notice.\n\nThat also keeps a bulk list on one queue by construction: every element of\na TCQ_F_ONETXQUEUE qdisc, including a follower changed by a filter, is\npinned to q-\u003edev_queue before it is appended. The fast bulk helper\ntherefore needs no head comparison and no skb_bad_txq requeue; the slow\nhelper, used only by non-ONETXQUEUE qdiscs, still compares and requeues a\nmismatched follower, where a wake on any queue reschedules q.\n\nOn the enqueue side taprio_enqueue() caps the mapping against\nreal_num_tx_queues and writes it back before selecting q-\u003eqdiscs[queue], so\na duplicating child cannot steer the clone out of the array.\n\nConditions to recreate the bug:\nThe dequeue path: load a SCHED_CLS or SCHED_ACT program that stores\n__sk_buff-\u003equeue_mapping (a tc BPF action is enough), attach it to a\ntransmit qdisc (for example a matchall filter on a prio root), and send a\npacket. With a 1-queue device a store of 1 indexes one past dev-\u003e_tx[].\nUnder KASAN with panic_on_warn=1 the unfixed kernel faults with \"BUG:\nKASAN: slab-out-\n---truncated---"
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:54.656Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/8182ba13500b39d75b66fe9f37e13cb325c4b17e"
},
{
"url": "https://git.kernel.org/stable/c/7445eccce376f7adb876c9f466d7d893344af7ce"
},
{
"url": "https://git.kernel.org/stable/c/7327092a678bfcb1bae033acb1be1006a1399e30"
},
{
"url": "https://git.kernel.org/stable/c/f19f2b308beb158d0e6f6eb806ced636e4ebf6ce"
}
],
"title": "net/sched: clamp skb-\u003equeue_mapping before indexing the tx queue",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99638",
"datePublished": "2026-11-20T05:49:54.656Z",
"dateReserved": "2026-09-25T10:25:14.426Z",
"dateUpdated": "2026-11-20T05:49:54.656Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99638",
"date": "2026-11-20",
"epss": "0.00176",
"percentile": "0.07264"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/sched/sch_generic.c",
"net/sched/sch_taprio.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8182ba13500b39d75b66fe9f37e13cb325c4b17e",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "7445eccce376f7adb876c9f466d7d893344af7ce",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "7327092a678bfcb1bae033acb1be1006a1399e30",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
},
{
"lessThan": "f19f2b308beb158d0e6f6eb806ced636e4ebf6ce",
"status": "affected",
"version": "74e31ca850c1cddeca03503171dd145b6ce293b6",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/sched/sch_generic.c",
"net/sched/sch_taprio.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.1"
},
{
"lessThan": "5.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: clamp skb-\u003equeue_mapping before indexing the tx queue\n\nThis issue was caught by Sashiko (nipa). A producer-side path cap is\nalready merged (ea4d4b5dddb5); this patch adds the matching consumer-side\ncaps.\n\nThe issue:\nThe tx queue is picked and capped in netdev_core_pick_tx() before the\n__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an\negress qdisc (not clsact) can then change __sk_buff-\u003equeue_mapping; that\nstore is never re-checked. bpf_convert_ctx_access() bounds it only by\nNO_QUEUE_MAPPING, not by the device\u0027s queue count.\n\nTwo consumers read the stale value:\n\n - On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which\n indexes dev-\u003e_tx[]. netdev_get_tx_queue() guards it with just a\n DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds\n txq-\u003e_xmit_lock and writes txq-\u003exmit_lock_owner past the end of the\n allocation on non-lltx devices such as ifb. Drivers that index their\n rings from skb_get_queue_mapping() (ex: ifb) go out of range the same\n way.\n\n - On enqueue, taprio_enqueue() indexes q-\u003eqdiscs[] with the same value;\n the array is sized dev-\u003enum_tx_queues. A duplicating netem on a child\n qdisc clones the skb and re-enqueues the clone at the taprio root\n (qdisc_root_bh()) through a direct rootq-\u003eenqueue() call, so the value\n reaches taprio_enqueue() before any dequeue cap runs.\n\nThe Fix:\nCap the mapping at the consumers and write the capped value back, so the\nqdisc\u0027s _tx[] lookup, the taprio q-\u003eqdiscs[] lookup and any later driver\nread stay in range.\n\nOn the dequeue side the cap folds into the dequeue path instead of a\nseparate walk over the returned list: dequeue_skb() caps the head, and\neach bulk helper caps the element it appends. For a qdisc that is not\nTCQ_F_ONETXQUEUE, netdev_cap_txqueue() logs a ratelimited notice and\nselects queue 0.\n\nA TCQ_F_ONETXQUEUE qdisc is bound to a single tx queue: dequeue_skb() uses\nq-\u003edev_queue for the frozen check, the BQL limit and the trace point, while\nqdisc_restart() transmits on the skb\u0027s queue. Capping an out-of-range\nmapping to queue 0 would therefore send a per-queue child\u0027s skb through a\ndifferent queue than the one it was dequeued for. On mq, mqprio, taprio and\nhtb offload children, a stopped queue 0 could then park the list in\nq-\u003egso_skb, and the later wake would schedule queue 0\u0027s own child instead\nof this qdisc. Pin a TCQ_F_ONETXQUEUE mapping to the qdisc\u0027s own queue to\nkeep the documented invariant.\n\nThe pin covers every mapping, not only an out-of-range one: an in-range\nmapping that a filter sets on one of those per-queue children is rewritten\nto the child\u0027s own queue, and this path does not call netdev_cap_txqueue(),\nso it logs no notice. On a single-queue device qdisc_create() sets\nTCQ_F_ONETXQUEUE, so the one-queue trigger described below also takes this\nbranch and is corrected without a notice.\n\nThat also keeps a bulk list on one queue by construction: every element of\na TCQ_F_ONETXQUEUE qdisc, including a follower changed by a filter, is\npinned to q-\u003edev_queue before it is appended. The fast bulk helper\ntherefore needs no head comparison and no skb_bad_txq requeue; the slow\nhelper, used only by non-ONETXQUEUE qdiscs, still compares and requeues a\nmismatched follower, where a wake on any queue reschedules q.\n\nOn the enqueue side taprio_enqueue() caps the mapping against\nreal_num_tx_queues and writes it back before selecting q-\u003eqdiscs[queue], so\na duplicating child cannot steer the clone out of the array.\n\nConditions to recreate the bug:\nThe dequeue path: load a SCHED_CLS or SCHED_ACT program that stores\n__sk_buff-\u003equeue_mapping (a tc BPF action is enough), attach it to a\ntransmit qdisc (for example a matchall filter on a prio root), and send a\npacket. With a 1-queue device a store of 1 indexes one past dev-\u003e_tx[].\nUnder KASAN with panic_on_warn=1 the unfixed kernel faults with \"BUG:\nKASAN: slab-out-\n---truncated---"
}
],
"id": "CVE-2026-99638",
"lastModified": "2026-11-20T06:17:57.087",
"metrics": {},
"published": "2026-11-20T06:17:57.087",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7327092a678bfcb1bae033acb1be1006a1399e30"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7445eccce376f7adb876c9f466d7d893344af7ce"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8182ba13500b39d75b66fe9f37e13cb325c4b17e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f19f2b308beb158d0e6f6eb806ced636e4ebf6ce"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:25:37+00:00",
"cve": "CVE-2026-99638",
"id": "CVE-2026-99638",
"initial_release_date": "2026-11-20T05:49:54.656000+00:00",
"product_status:known_affected": "176",
"product_status:known_not_affected": "28",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via unvalidated queue mapping in traffic control",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99638.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.