CVE-2026-99681 (GCVE-0-2026-99681)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:50 – Updated: 2026-11-20 05:50| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
04225d13aef11b2a539014def5e47d8c21fd74a5 , < a66d71dddc041ddf02c0476778573c5dba30f758
(git)
Affected: 04225d13aef11b2a539014def5e47d8c21fd74a5 , < 92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae (git) Affected: 04225d13aef11b2a539014def5e47d8c21fd74a5 , < 894e4e6084924cfd590968d45fad20908e02ddae (git) Affected: e01facfb54a9b2e1ad7bbb00601a42b16d276d81 (git) Affected: 6.16.4 , < 6.17 (semver) |
guessed | |
| Linux | Linux |
Affected:
6.17
Unaffected: 0 , < 6.17 (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": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a66d71dddc041ddf02c0476778573c5dba30f758",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"lessThan": "92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"lessThan": "894e4e6084924cfd590968d45fad20908e02ddae",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"status": "affected",
"version": "e01facfb54a9b2e1ad7bbb00601a42b16d276d81",
"versionType": "git"
},
{
"lessThan": "6.17",
"status": "affected",
"version": "6.16.4",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"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.18.64",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.16.4",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: fix out-of-bounds read in blk_mq_free_rqs\n\nA KASAN slab-out-of-bounds read can occur in blk_mq_free_rqs() when there\nis a mismatch between the number of hardware queues allocated for the IO\nscheduler (et-\u003enr_hw_queues) and the number of hardware queues in the block\ntag set (set-\u003enr_hw_queues).\n\nThis mismatch can happen if blk_mq_update_nr_hw_queues() fails halfway\nthrough (e.g., due to memory pressure during\nblk_mq_prealloc_tag_set_tags()). In this error path, the elevator is\nrestored with a larger number of hardware queues than the block tag set\nactually has.\n\nWhen the elevator is later freed, blk_mq_free_sched_tags() iterates up to\nthe new et-\u003enr_hw_queues and calls blk_mq_free_rqs(). In blk_mq_free_rqs(),\nit attempts to access set-\u003etags[hctx_idx] to get the driver tags. Because\nset-\u003enr_hw_queues was not updated due to the earlier failure, set-\u003etags\nstill has the old (smaller) size, leading to an out-of-bounds read.\n\nBUG: KASAN: slab-out-of-bounds in blk_mq_free_rqs+0xde/0x680\nRead of size 8 at addr ffff88818d67fc28 by task syz-executor117/5839\nCall Trace:\n blk_mq_free_rqs+0xde/0x680\n blk_mq_free_map_and_rqs+0x40/0xf0\n blk_mq_free_sched_tags\n blk_mq_free_sched_res+0xeb/0x280\n elevator_change_done+0x1d2/0x5c0\n elevator_change+0x34f/0x480\n elv_iosched_store+0x504/0x630\n queue_attr_store+0x207/0x2b0\n\nTo fix this, explicitly check if hctx_idx \u003c set-\u003enr_hw_queues before\naccessing set-\u003etags[hctx_idx]. If hctx_idx \u003e= set-\u003enr_hw_queues, the\nhardware queue doesn\u0027t exist in the tag set, meaning there are no driver\ntags to clear mappings from. In this case, safely set drv_tags to NULL. The\nsubsequent call to blk_mq_clear_rq_mapping() already handles a NULL\ndrv_tags pointer and will safely return."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:50:27.952Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/a66d71dddc041ddf02c0476778573c5dba30f758"
},
{
"url": "https://git.kernel.org/stable/c/92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae"
},
{
"url": "https://git.kernel.org/stable/c/894e4e6084924cfd590968d45fad20908e02ddae"
}
],
"title": "blk-mq: fix out-of-bounds read in blk_mq_free_rqs",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99681",
"datePublished": "2026-11-20T05:50:27.952Z",
"dateReserved": "2026-09-25T10:25:14.428Z",
"dateUpdated": "2026-11-20T05:50:27.952Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99681",
"date": "2026-11-20",
"epss": "0.00166",
"percentile": "0.06024"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a66d71dddc041ddf02c0476778573c5dba30f758",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"lessThan": "92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"lessThan": "894e4e6084924cfd590968d45fad20908e02ddae",
"status": "affected",
"version": "04225d13aef11b2a539014def5e47d8c21fd74a5",
"versionType": "git"
},
{
"status": "affected",
"version": "e01facfb54a9b2e1ad7bbb00601a42b16d276d81",
"versionType": "git"
},
{
"lessThan": "6.17",
"status": "affected",
"version": "6.16.4",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"block/blk-mq.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"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\nblk-mq: fix out-of-bounds read in blk_mq_free_rqs\n\nA KASAN slab-out-of-bounds read can occur in blk_mq_free_rqs() when there\nis a mismatch between the number of hardware queues allocated for the IO\nscheduler (et-\u003enr_hw_queues) and the number of hardware queues in the block\ntag set (set-\u003enr_hw_queues).\n\nThis mismatch can happen if blk_mq_update_nr_hw_queues() fails halfway\nthrough (e.g., due to memory pressure during\nblk_mq_prealloc_tag_set_tags()). In this error path, the elevator is\nrestored with a larger number of hardware queues than the block tag set\nactually has.\n\nWhen the elevator is later freed, blk_mq_free_sched_tags() iterates up to\nthe new et-\u003enr_hw_queues and calls blk_mq_free_rqs(). In blk_mq_free_rqs(),\nit attempts to access set-\u003etags[hctx_idx] to get the driver tags. Because\nset-\u003enr_hw_queues was not updated due to the earlier failure, set-\u003etags\nstill has the old (smaller) size, leading to an out-of-bounds read.\n\nBUG: KASAN: slab-out-of-bounds in blk_mq_free_rqs+0xde/0x680\nRead of size 8 at addr ffff88818d67fc28 by task syz-executor117/5839\nCall Trace:\n blk_mq_free_rqs+0xde/0x680\n blk_mq_free_map_and_rqs+0x40/0xf0\n blk_mq_free_sched_tags\n blk_mq_free_sched_res+0xeb/0x280\n elevator_change_done+0x1d2/0x5c0\n elevator_change+0x34f/0x480\n elv_iosched_store+0x504/0x630\n queue_attr_store+0x207/0x2b0\n\nTo fix this, explicitly check if hctx_idx \u003c set-\u003enr_hw_queues before\naccessing set-\u003etags[hctx_idx]. If hctx_idx \u003e= set-\u003enr_hw_queues, the\nhardware queue doesn\u0027t exist in the tag set, meaning there are no driver\ntags to clear mappings from. In this case, safely set drv_tags to NULL. The\nsubsequent call to blk_mq_clear_rq_mapping() already handles a NULL\ndrv_tags pointer and will safely return."
}
],
"id": "CVE-2026-99681",
"lastModified": "2026-11-20T06:18:02.973",
"metrics": {},
"published": "2026-11-20T06:18:02.973",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/894e4e6084924cfd590968d45fad20908e02ddae"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/92ea40ca224ca9909dc7a5ac80dfb3e7cb0e6cae"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a66d71dddc041ddf02c0476778573c5dba30f758"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T08:03:02+00:00",
"cve": "CVE-2026-99681",
"id": "CVE-2026-99681",
"initial_release_date": "2026-11-20T05:50:27.952000+00:00",
"product_status:known_affected": "111",
"product_status:known_not_affected": "93",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via out-of-bounds read in blk-mq",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99681.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.