FKIE_CVE-2026-99750
Vulnerability from fkie_nvd - Published: 2026-11-20 06:18 - Updated: 2026-11-20 06:18| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "cc71e3abb81ae1470c09acae85d989b42509a2e0",
"status": "affected",
"version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
"versionType": "git"
},
{
"lessThan": "2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030",
"status": "affected",
"version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
"versionType": "git"
},
{
"lessThan": "7e9a78223752911e118710009aab9dd9e10b2ee7",
"status": "affected",
"version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
"versionType": "git"
},
{
"lessThan": "1dd91081ba3c692565f9c1f884149178d5a06d1e",
"status": "affected",
"version": "e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/smb/server/smb2pdu.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.15"
},
{
"lessThan": "5.15",
"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\nksmbd: require DELETE access for delete-on-close opens\n\nsmb2_open() accepts FILE_DELETE_ON_CLOSE on an existing file without\nDELETE in DesiredAccess. When the request asks only for\nFILE_READ_ATTRIBUTES or READ_CONTROL, it also skips inode_permission()\nand the parent directory MAY_WRITE | MAY_EXEC check that delete-on-close\nis meant to get. The file is then marked for deletion by a caller who\ncould not delete it.\n\nThe unlink happens later, in __ksmbd_inode_close(), when the last handle\non the inode is closed, and it runs with the credentials of that handle.\nIf the caller closes last, the unlink fails. If another user who can\nwrite the parent directory, such as the file\u0027s owner, still has the file\nopen, the file is deleted when that user closes it. Until then new opens\nof the file fail with STATUS_DELETE_PENDING. So a user with only search\npermission on a directory can delete a file in it, or block opens of it,\nwhile the owner has it open.\n\nA MAXIMUM_ALLOWED open that also requests DELETE has the same problem.\nThe requested access is replaced with the maximal access, which does not\ninclude DELETE when the caller cannot write the parent directory, and the\nlater permission checks are skipped as already done.\n\nMS-FSA 2.1.5.1 requires an open with FILE_DELETE_ON_CLOSE and without\nDELETE in DesiredAccess to fail with STATUS_INVALID_PARAMETER, and Samba\ndoes the same. Add that check to the CreateOptions validation, using\nthe generic-mapped DesiredAccess so that GENERIC_ALL still qualifies.\nThis also refuses MAXIMUM_ALLOWED with FILE_DELETE_ON_CLOSE but no\nexplicit DELETE, as MS-FSA and Samba do. When MAXIMUM_ALLOWED is\nrequested with DELETE but the maximal access does not include DELETE,\nfail with STATUS_ACCESS_DENIED. With DELETE requested, delete-on-close\nopens go through the existing parent directory check."
}
],
"id": "CVE-2026-99750",
"lastModified": "2026-11-20T06:18:12.990",
"metrics": {},
"published": "2026-11-20T06:18:12.990",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/1dd91081ba3c692565f9c1f884149178d5a06d1e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2d0d4adb6bade8b204b10ad2a4c43f3b7d2af030"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7e9a78223752911e118710009aab9dd9e10b2ee7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cc71e3abb81ae1470c09acae85d989b42509a2e0"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
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.