FKIE_CVE-2026-99357
Vulnerability from fkie_nvd - Published: 2026-11-19 15:17 - Updated: 2026-11-19 15:17| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/sunrpc/svc_xprt.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "629a17cc81fe0b749bbee8303797b6c99a3e776b",
"status": "affected",
"version": "260c1d1298f6703d38fdccd3dd5a310766327340",
"versionType": "git"
},
{
"lessThan": "d514dd81771aff1192e84a57ae60428c13f07ccb",
"status": "affected",
"version": "260c1d1298f6703d38fdccd3dd5a310766327340",
"versionType": "git"
},
{
"lessThan": "70614e41d379e5b9b1893ac65b49ae4cea6c36eb",
"status": "affected",
"version": "260c1d1298f6703d38fdccd3dd5a310766327340",
"versionType": "git"
},
{
"lessThan": "2192a56b0686599358909c3e12e9a366f5b5d452",
"status": "affected",
"version": "260c1d1298f6703d38fdccd3dd5a310766327340",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/sunrpc/svc_xprt.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.25"
},
{
"lessThan": "2.6.25",
"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\nSUNRPC: Copy the deferred RPC Call from the head buffer\n\nsvc_defer() snapshots the RPC Call for replay once a pending cache\nupcall resolves. It copies the Call starting (rq_arg.len -\nhead[0].iov_len) bytes before head[0].iov_base, a back-up that once\ncovered a transport header. No transport has had one since commit\n983084b2672c (\"SUNRPC: Remove svc_rqst::rq_xprt_hlen\"), so the two\nlengths are meant to be equal.\n\nAn RPCSEC_GSS Call breaks that assumption. Unwrapping the integrity\nservice truncates rq_arg.len by the length of the trailing checksum,\nand unwrapping the privacy service leaves rq_arg.len short by an\namount the client sets with trailing bytes after the wrap token.\nNeither adjusts head[0].iov_len. Both lengths are size_t, so the\nsubtraction underflows and the copy starts past head[0].iov_base.\nEvery deferred integrity Call replays a shifted snapshot.\n\nA deferred replay skips GSS verification, so a shifted snapshot runs\nas an authenticated Call. With the privacy service the offset is\nclient-chosen. A forged Call placed in that window, naming another\nuser\u0027s GSS context handle, runs under that identity.\n\nCopy the Call from head[0].iov_base. Refuse to defer a Call whose\nlength runs past the head buffer, so the copy cannot read out of\nbounds."
}
],
"id": "CVE-2026-99357",
"lastModified": "2026-11-19T15:17:47.197",
"metrics": {},
"published": "2026-11-19T15:17:47.197",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2192a56b0686599358909c3e12e9a366f5b5d452"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/629a17cc81fe0b749bbee8303797b6c99a3e776b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/70614e41d379e5b9b1893ac65b49ae4cea6c36eb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d514dd81771aff1192e84a57ae60428c13f07ccb"
}
],
"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.