CVE-2026-99366 (GCVE-0-2026-99366)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:22 – Updated: 2026-11-19 14:37| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
cc028a10a48c3c555d7772d02f56eea9f86fdf79 , < 065764e256ebff20201dca5bc6ff075c6cb62e17
(git)
Affected: cc028a10a48c3c555d7772d02f56eea9f86fdf79 , < 0b5149b7ad8ccd64c61e887e2cf1af068b6210c9 (git) Affected: cc028a10a48c3c555d7772d02f56eea9f86fdf79 , < 4e3c12151f13c4e51eb381f9377835fb94b9f56a (git) Affected: cc028a10a48c3c555d7772d02f56eea9f86fdf79 , < 2987838317501ff67b672ac2a441fe34b7729f3d (git) |
guessed | |
| Linux | Linux |
Affected:
5.10
Unaffected: 0 , < 5.10 (semver) Unaffected: 6.12.117 , ≤ 6.12.* (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/nfsd/nfs4state.c",
"fs/nfsd/xdr4.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "065764e256ebff20201dca5bc6ff075c6cb62e17",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "0b5149b7ad8ccd64c61e887e2cf1af068b6210c9",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "4e3c12151f13c4e51eb381f9377835fb94b9f56a",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "2987838317501ff67b672ac2a441fe34b7729f3d",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/nfsd/nfs4state.c",
"fs/nfsd/xdr4.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.10"
},
{
"lessThan": "5.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"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.12.117",
"versionStartIncluding": "5.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "5.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "5.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "5.10",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: don\u0027t modify a session slot when replaying its cached reply\n\nnfsd4_sequence() claims a session slot by setting NFSD4_SLOT_INUSE\nunder nn-\u003eclient_lock. A reply served from the slot\u0027s reply cache does\nnot claim it, and that distinction lived only in cstate-\u003estatus, which\nnfsd4_sequence() set to nfserr_replay_cache. Commit cc028a10a48c\n(\"NFSD: Hoist status code encoding into XDR encoder functions\") moved\nnfsd4_proc_compound()\u0027s cstate-\u003estatus assignment below the out:\nlabel, and the replay path\u0027s goto out was the one path that relied on\nskipping it. The test in nfsd4_sequence_done() therefore no longer\nidentifies a replay, and every replay now stores its reply and clears\nNFSD4_SLOT_INUSE as though it owned the slot.\n\nNFSD4_SLOT_INUSE is the interlock: check_slot_seqid() rejects every\nsequence id for a slot that is in use, before replay_matches_cache()\nruns. A replay never sets it, so two replays can be in flight on the\nsame slot at once. One can read slot-\u003esl_cred under nn-\u003eclient_lock\nwhile the other\u0027s completion frees and rebuilds it from the XDR\nencoder without that lock. Two completions can also collide with each\nother and release the same group_info twice. free_svc_cred() leaves\ncr_uid, cr_gid and cr_flavor intact, so the reader passes every\nearlier test in same_creds() and dereferences a NULL cr_group_info.\nFrom a 6.12.91 production server:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000004\n CPU: 63 UID: 0 PID: 39015 Comm: nfsd\n RIP: 0010:same_creds+0x38/0xa0 [nfsd]\n RDX: 0000000000000000\n Call Trace:\n nfsd4_sequence+0x6a8/0x910 [nfsd]\n nfsd4_proc_compound+0x345/0x670 [nfsd]\n nfsd_dispatch+0x100/0x220 [nfsd]\n svc_process_common+0x311/0x700 [sunrpc]\n svc_process+0x131/0x1c0 [sunrpc]\n svc_recv+0x7ef/0x9c0 [sunrpc]\n nfsd+0xa3/0x100 [nfsd]\n Kernel panic - not syncing: Fatal exception\n\nSince v6.14 a live session\u0027s slot table can shrink, and the unowned\nstore becomes a use-after-free write. nfsd4_sequence() defers the\nshrink while a slot is in use, but it tests NFSD4_SLOT_INUSE, which a\nreplay does not set, so free_session_slots() can kfree() the slot the\nreplay still holds in cstate-\u003eslot.\n\nRecord the claim in cstate-\u003eslot_owned when nfsd4_sequence() accepts a\nrequest and test that in nfsd4_sequence_done(), so only the request\nthat claimed the slot updates its cached reply and clears\nNFSD4_SLOT_INUSE. svc_generic_init_request() zeroes the compound\nresponse before each request, so the flag starts clear."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:37:50.515Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/065764e256ebff20201dca5bc6ff075c6cb62e17"
},
{
"url": "https://git.kernel.org/stable/c/0b5149b7ad8ccd64c61e887e2cf1af068b6210c9"
},
{
"url": "https://git.kernel.org/stable/c/4e3c12151f13c4e51eb381f9377835fb94b9f56a"
},
{
"url": "https://git.kernel.org/stable/c/2987838317501ff67b672ac2a441fe34b7729f3d"
}
],
"title": "nfsd: don\u0027t modify a session slot when replaying its cached reply",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99366",
"datePublished": "2026-11-19T14:22:57.262Z",
"dateReserved": "2026-09-25T10:25:14.410Z",
"dateUpdated": "2026-11-19T14:37:50.515Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99366",
"date": "2026-11-20",
"epss": "0.00215",
"percentile": "0.12151"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/nfsd/nfs4state.c",
"fs/nfsd/xdr4.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "065764e256ebff20201dca5bc6ff075c6cb62e17",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "0b5149b7ad8ccd64c61e887e2cf1af068b6210c9",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "4e3c12151f13c4e51eb381f9377835fb94b9f56a",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
},
{
"lessThan": "2987838317501ff67b672ac2a441fe34b7729f3d",
"status": "affected",
"version": "cc028a10a48c3c555d7772d02f56eea9f86fdf79",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/nfsd/nfs4state.c",
"fs/nfsd/xdr4.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.10"
},
{
"lessThan": "5.10",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.117",
"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\nnfsd: don\u0027t modify a session slot when replaying its cached reply\n\nnfsd4_sequence() claims a session slot by setting NFSD4_SLOT_INUSE\nunder nn-\u003eclient_lock. A reply served from the slot\u0027s reply cache does\nnot claim it, and that distinction lived only in cstate-\u003estatus, which\nnfsd4_sequence() set to nfserr_replay_cache. Commit cc028a10a48c\n(\"NFSD: Hoist status code encoding into XDR encoder functions\") moved\nnfsd4_proc_compound()\u0027s cstate-\u003estatus assignment below the out:\nlabel, and the replay path\u0027s goto out was the one path that relied on\nskipping it. The test in nfsd4_sequence_done() therefore no longer\nidentifies a replay, and every replay now stores its reply and clears\nNFSD4_SLOT_INUSE as though it owned the slot.\n\nNFSD4_SLOT_INUSE is the interlock: check_slot_seqid() rejects every\nsequence id for a slot that is in use, before replay_matches_cache()\nruns. A replay never sets it, so two replays can be in flight on the\nsame slot at once. One can read slot-\u003esl_cred under nn-\u003eclient_lock\nwhile the other\u0027s completion frees and rebuilds it from the XDR\nencoder without that lock. Two completions can also collide with each\nother and release the same group_info twice. free_svc_cred() leaves\ncr_uid, cr_gid and cr_flavor intact, so the reader passes every\nearlier test in same_creds() and dereferences a NULL cr_group_info.\nFrom a 6.12.91 production server:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000004\n CPU: 63 UID: 0 PID: 39015 Comm: nfsd\n RIP: 0010:same_creds+0x38/0xa0 [nfsd]\n RDX: 0000000000000000\n Call Trace:\n nfsd4_sequence+0x6a8/0x910 [nfsd]\n nfsd4_proc_compound+0x345/0x670 [nfsd]\n nfsd_dispatch+0x100/0x220 [nfsd]\n svc_process_common+0x311/0x700 [sunrpc]\n svc_process+0x131/0x1c0 [sunrpc]\n svc_recv+0x7ef/0x9c0 [sunrpc]\n nfsd+0xa3/0x100 [nfsd]\n Kernel panic - not syncing: Fatal exception\n\nSince v6.14 a live session\u0027s slot table can shrink, and the unowned\nstore becomes a use-after-free write. nfsd4_sequence() defers the\nshrink while a slot is in use, but it tests NFSD4_SLOT_INUSE, which a\nreplay does not set, so free_session_slots() can kfree() the slot the\nreplay still holds in cstate-\u003eslot.\n\nRecord the claim in cstate-\u003eslot_owned when nfsd4_sequence() accepts a\nrequest and test that in nfsd4_sequence_done(), so only the request\nthat claimed the slot updates its cached reply and clears\nNFSD4_SLOT_INUSE. svc_generic_init_request() zeroes the compound\nresponse before each request, so the flag starts clear."
}
],
"id": "CVE-2026-99366",
"lastModified": "2026-11-19T15:17:48.317",
"metrics": {},
"published": "2026-11-19T15:17:48.317",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/065764e256ebff20201dca5bc6ff075c6cb62e17"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0b5149b7ad8ccd64c61e887e2cf1af068b6210c9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2987838317501ff67b672ac2a441fe34b7729f3d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4e3c12151f13c4e51eb381f9377835fb94b9f56a"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Important",
"current_release_date": "2026-11-19T16:40:58+00:00",
"cve": "CVE-2026-99366",
"id": "CVE-2026-99366",
"initial_release_date": "2026-11-19T14:22:57.262000+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 concurrent session slot replays in nfsd",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99366.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.