CVE-2026-99380 (GCVE-0-2026-99380)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:23 – Updated: 2026-11-19 14:38| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c , < 520b48753e3c54172a078e7e4b82aec83ae2e08d
(git)
Affected: 0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c , < d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052 (git) Affected: 0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c , < 83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7 (git) |
guessed | |
| Linux | Linux |
Affected:
2.6.16
Unaffected: 0 , < 2.6.16 (semver) Unaffected: 6.18.61 , ≤ 6.18.* (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/client/cifssmb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "520b48753e3c54172a078e7e4b82aec83ae2e08d",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
},
{
"lessThan": "d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
},
{
"lessThan": "83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/smb/client/cifssmb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.16"
},
{
"lessThan": "2.6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"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": "6.18.61",
"versionStartIncluding": "2.6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "2.6.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "2.6.16",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: validate NT transaction response layout and offsets\n\nvalidate_ntransact() assumes that the response uses the fixed 18-word NT\ntransaction layout. A different WordCount makes get_bcc() locate the byte\ncount at a different offset from pSMBr-\u003eByteCount, allowing the subsequent\nbounds checks to use inconsistent response boundaries.\n\nThe function also turns the 32-bit ParameterOffset and DataOffset fields\ninto pointers before checking their bounds. On a 32-bit client, a large\noffset can wrap the pointer below end_of_smb and pass the one-sided pointer\ncomparison. The caller then dereferences the parameter pointer or copies\nfrom the data pointer.\n\nRequire the expected WordCount before reading the byte count. Check each\noffset and count against the received SMB length as integers before forming\neither pointer. Use subtraction after validating the offset so that the\nrange checks cannot overflow."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:38:25.577Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/520b48753e3c54172a078e7e4b82aec83ae2e08d"
},
{
"url": "https://git.kernel.org/stable/c/d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052"
},
{
"url": "https://git.kernel.org/stable/c/83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7"
}
],
"title": "smb: client: validate NT transaction response layout and offsets",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99380",
"datePublished": "2026-11-19T14:23:20.787Z",
"dateReserved": "2026-09-25T10:25:14.411Z",
"dateUpdated": "2026-11-19T14:38:25.577Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99380",
"date": "2026-11-20",
"epss": "0.00222",
"percentile": "0.13062"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/smb/client/cifssmb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "520b48753e3c54172a078e7e4b82aec83ae2e08d",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
},
{
"lessThan": "d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
},
{
"lessThan": "83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7",
"status": "affected",
"version": "0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/smb/client/cifssmb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.16"
},
{
"lessThan": "2.6.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.61",
"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\nsmb: client: validate NT transaction response layout and offsets\n\nvalidate_ntransact() assumes that the response uses the fixed 18-word NT\ntransaction layout. A different WordCount makes get_bcc() locate the byte\ncount at a different offset from pSMBr-\u003eByteCount, allowing the subsequent\nbounds checks to use inconsistent response boundaries.\n\nThe function also turns the 32-bit ParameterOffset and DataOffset fields\ninto pointers before checking their bounds. On a 32-bit client, a large\noffset can wrap the pointer below end_of_smb and pass the one-sided pointer\ncomparison. The caller then dereferences the parameter pointer or copies\nfrom the data pointer.\n\nRequire the expected WordCount before reading the byte count. Check each\noffset and count against the received SMB length as integers before forming\neither pointer. Use subtraction after validating the offset so that the\nrange checks cannot overflow."
}
],
"id": "CVE-2026-99380",
"lastModified": "2026-11-19T15:17:50.050",
"metrics": {},
"published": "2026-11-19T15:17:50.050",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/520b48753e3c54172a078e7e4b82aec83ae2e08d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T21:02:59+00:00",
"cve": "CVE-2026-99380",
"id": "CVE-2026-99380",
"initial_release_date": "2026-11-19T14:23:20.787000+00:00",
"product_status:known_affected": "162",
"product_status:known_not_affected": "42",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via crafted SMB NT transaction response",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99380.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.