CVE-2026-99322 (GCVE-0-2026-99322)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:21 – Updated: 2026-11-19 14:33| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac , < 7b54fe3db87bc3dee16c66b400206978e515a705
(git)
Affected: bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac , < 864bbcd5dc5e70d639a3011eae81a872b69ff402 (git) Affected: c2b867861a48f0438afa6ce01f75e414df5431ad (git) Affected: 7.2.6 , < 7.3 (semver) |
guessed | |
| Linux | Linux |
Affected:
7.3
Unaffected: 0 , < 7.3 (semver) Unaffected: 7.3.2 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c",
"fs/smb/server/vfs_cache.c",
"fs/smb/server/vfs_cache.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "7b54fe3db87bc3dee16c66b400206978e515a705",
"status": "affected",
"version": "bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac",
"versionType": "git"
},
{
"lessThan": "864bbcd5dc5e70d639a3011eae81a872b69ff402",
"status": "affected",
"version": "bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac",
"versionType": "git"
},
{
"status": "affected",
"version": "c2b867861a48f0438afa6ce01f75e414df5431ad",
"versionType": "git"
},
{
"lessThan": "7.3",
"status": "affected",
"version": "7.2.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c",
"fs/smb/server/vfs_cache.c",
"fs/smb/server/vfs_cache.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.3"
},
{
"lessThan": "7.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "7.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "7.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "7.2.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: rebind completed CREATE replays without draining the old channel\n\nA completed DurableHandleReqV2 CREATE can be replayed through another\nchannel while its original channel is exiting. The existing replay path\nreturns the open but leaves its connection and oplock references pointing\nat the old channel. Its open count also stays on that channel, and a\nlater CLOSE through the surviving channel decrements the wrong counter.\n\nAfter checking the owner, lease key and persistent flag, verify that an\nactive open is still published in the requesting session\u0027s file table.\nDo this even when no oplock was granted, and before processing a consumed\nreplay. Do not read a borrowed opinfo session pointer for this check.\n\nKeep a healthy original binding. If the original channel is exiting or\nreleasing, move the open and its own oplock references to the requesting\nchannel. Serialize this with CLOSE using the session file-table lock,\nand with detach, reconnect and notification snapshots using m_lock.\nThe earlier lock index and lease-table changes make their lifetimes\nindependent of this connection change. No old-channel r_count wait is\nneeded, including when an unrelated request remains active there.\n\nAccount final close against fp-\u003econn in one place, balance durable detach\nand reconnect, and transfer the count with a replay binding change. A\nfinal global lookup put may run after CLOSE has removed the volatile id;\nunlink the open from the inode list on that final close as well.\n\nA live completed CREATE replay may follow a break that lowered the\ndurable open\u0027s batch oplock. Apply the batch eligibility check only to\ndetached reconnects, while retaining the owner, lease key and persistent\nflag checks for active replays."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:33:15.423Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/7b54fe3db87bc3dee16c66b400206978e515a705"
},
{
"url": "https://git.kernel.org/stable/c/864bbcd5dc5e70d639a3011eae81a872b69ff402"
}
],
"title": "ksmbd: rebind completed CREATE replays without draining the old channel",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99322",
"datePublished": "2026-11-19T14:21:30.827Z",
"dateReserved": "2026-09-25T10:25:14.408Z",
"dateUpdated": "2026-11-19T14:33:15.423Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c",
"fs/smb/server/vfs_cache.c",
"fs/smb/server/vfs_cache.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "7b54fe3db87bc3dee16c66b400206978e515a705",
"status": "affected",
"version": "bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac",
"versionType": "git"
},
{
"lessThan": "864bbcd5dc5e70d639a3011eae81a872b69ff402",
"status": "affected",
"version": "bb8bf7eb13b518b379356a0c5dee8a23d6ee37ac",
"versionType": "git"
},
{
"status": "affected",
"version": "c2b867861a48f0438afa6ce01f75e414df5431ad",
"versionType": "git"
},
{
"lessThan": "7.3",
"status": "affected",
"version": "7.2.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c",
"fs/smb/server/vfs_cache.c",
"fs/smb/server/vfs_cache.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.3"
},
{
"lessThan": "7.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"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\nksmbd: rebind completed CREATE replays without draining the old channel\n\nA completed DurableHandleReqV2 CREATE can be replayed through another\nchannel while its original channel is exiting. The existing replay path\nreturns the open but leaves its connection and oplock references pointing\nat the old channel. Its open count also stays on that channel, and a\nlater CLOSE through the surviving channel decrements the wrong counter.\n\nAfter checking the owner, lease key and persistent flag, verify that an\nactive open is still published in the requesting session\u0027s file table.\nDo this even when no oplock was granted, and before processing a consumed\nreplay. Do not read a borrowed opinfo session pointer for this check.\n\nKeep a healthy original binding. If the original channel is exiting or\nreleasing, move the open and its own oplock references to the requesting\nchannel. Serialize this with CLOSE using the session file-table lock,\nand with detach, reconnect and notification snapshots using m_lock.\nThe earlier lock index and lease-table changes make their lifetimes\nindependent of this connection change. No old-channel r_count wait is\nneeded, including when an unrelated request remains active there.\n\nAccount final close against fp-\u003econn in one place, balance durable detach\nand reconnect, and transfer the count with a replay binding change. A\nfinal global lookup put may run after CLOSE has removed the volatile id;\nunlink the open from the inode list on that final close as well.\n\nA live completed CREATE replay may follow a break that lowered the\ndurable open\u0027s batch oplock. Apply the batch eligibility check only to\ndetached reconnects, while retaining the owner, lease key and persistent\nflag checks for active replays."
}
],
"id": "CVE-2026-99322",
"lastModified": "2026-11-19T15:17:42.937",
"metrics": {},
"published": "2026-11-19T15:17:42.937",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7b54fe3db87bc3dee16c66b400206978e515a705"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/864bbcd5dc5e70d639a3011eae81a872b69ff402"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:01:57+00:00",
"cve": "CVE-2026-99322",
"id": "CVE-2026-99322",
"initial_release_date": "2026-11-19T14:21:30.827000+00:00",
"product_status:known_not_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: ksmbd: Denial of service via improper channel rebinding during request replay",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99322.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.