CVE-2026-99350 (GCVE-0-2026-99350)
Vulnerability from cvelistv5 – Published: 2026-11-19 14:22 – Updated: 2026-11-19 14:36| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
b0f571ecd7943423c25947439045f0d352ca3dbf , < 35f7a69391ca0819d04ca6db3c2355848d633e16
(git)
Affected: b0f571ecd7943423c25947439045f0d352ca3dbf , < 965456110cf6952cc4eec80761171503e6e424df (git) Affected: b0f571ecd7943423c25947439045f0d352ca3dbf , < ec98e8bdbde85e2dd2d43570e25b52bdfac1735b (git) Affected: b0f571ecd7943423c25947439045f0d352ca3dbf , < 7801c42c3bb737cfb06194a383873fcad8daacf5 (git) Affected: 79e2ca7aa96e80961828ab6312264633b66183cc (git) Affected: 2bc769b8edb158be7379d15f36e23d66cf850053 (git) Affected: 091dc91e119fdd61432347231724f4e861c6b465 (git) Affected: 5.10.140 , < 5.11 (semver) Affected: 5.15.64 , < 5.16 (semver) Affected: 5.19.6 , < 5.20 (semver) |
guessed | |
| Linux | Linux |
Affected:
6.0
Unaffected: 0 , < 6.0 (semver) Unaffected: 6.12.118 , ≤ 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": [
"net/rxrpc/sendmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "35f7a69391ca0819d04ca6db3c2355848d633e16",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "965456110cf6952cc4eec80761171503e6e424df",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "ec98e8bdbde85e2dd2d43570e25b52bdfac1735b",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "7801c42c3bb737cfb06194a383873fcad8daacf5",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"status": "affected",
"version": "79e2ca7aa96e80961828ab6312264633b66183cc",
"versionType": "git"
},
{
"status": "affected",
"version": "2bc769b8edb158be7379d15f36e23d66cf850053",
"versionType": "git"
},
{
"status": "affected",
"version": "091dc91e119fdd61432347231724f4e861c6b465",
"versionType": "git"
},
{
"lessThan": "5.11",
"status": "affected",
"version": "5.10.140",
"versionType": "semver"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.64",
"versionType": "semver"
},
{
"lessThan": "5.20",
"status": "affected",
"version": "5.19.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/rxrpc/sendmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.0"
},
{
"lessThan": "6.0",
"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.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.118",
"versionStartIncluding": "6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.61",
"versionStartIncluding": "6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.2",
"versionStartIncluding": "6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"versionStartIncluding": "6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.10.140",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.15.64",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.19.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: Fix update of call-\u003etx_pending without holding lock\n\nCurrently, rxrpc_send_data() updates call-\u003etx_pending just before it\nreturns - but it won\u0027t be holding the call-\u003euser_mutex when it does this if\na wait was interrupted by a signal. This would allow a parallel sendmsg()\nto race.\n\nFurther, both the callers of rxrpc_send_data() call it with the lock held,\nand then it returns an indication through the parameter list to say whether\nit has dropped the lock or not - after which the callers both just drop the\nlock if it\u0027s still held.\n\nFix this by:\n\n (1) Moving the release of call-\u003euser_mutex down into rxrpc_send_data() and\n get rid of the indicator parameter. This makes it easier to see where\n the lock is held.\n\n (2) After waiting, if the attempt to reacquire the mutex is interrupted,\n just return directly there rather than going to out_unlock\n\n (3) Restricting the txb variable to inside the buffering loop and leaving\n -\u003etx_pending set until we\u0027ve queued the buffer.\n\nNote that there\u0027s a slight change in behaviour in that wait_for_space\nfailure now doesn\u0027t check for completion because it doesn\u0027t hold the call\nuser_mutex. The caller, however, should re-issue the send and pick up any\nerror at a second attempt."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T14:36:51.398Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/35f7a69391ca0819d04ca6db3c2355848d633e16"
},
{
"url": "https://git.kernel.org/stable/c/965456110cf6952cc4eec80761171503e6e424df"
},
{
"url": "https://git.kernel.org/stable/c/ec98e8bdbde85e2dd2d43570e25b52bdfac1735b"
},
{
"url": "https://git.kernel.org/stable/c/7801c42c3bb737cfb06194a383873fcad8daacf5"
}
],
"title": "rxrpc: Fix update of call-\u003etx_pending without holding lock",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99350",
"datePublished": "2026-11-19T14:22:10.838Z",
"dateReserved": "2026-09-25T10:25:14.409Z",
"dateUpdated": "2026-11-19T14:36:51.398Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/rxrpc/sendmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "35f7a69391ca0819d04ca6db3c2355848d633e16",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "965456110cf6952cc4eec80761171503e6e424df",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "ec98e8bdbde85e2dd2d43570e25b52bdfac1735b",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"lessThan": "7801c42c3bb737cfb06194a383873fcad8daacf5",
"status": "affected",
"version": "b0f571ecd7943423c25947439045f0d352ca3dbf",
"versionType": "git"
},
{
"status": "affected",
"version": "79e2ca7aa96e80961828ab6312264633b66183cc",
"versionType": "git"
},
{
"status": "affected",
"version": "2bc769b8edb158be7379d15f36e23d66cf850053",
"versionType": "git"
},
{
"status": "affected",
"version": "091dc91e119fdd61432347231724f4e861c6b465",
"versionType": "git"
},
{
"lessThan": "5.11",
"status": "affected",
"version": "5.10.140",
"versionType": "semver"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.64",
"versionType": "semver"
},
{
"lessThan": "5.20",
"status": "affected",
"version": "5.19.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/rxrpc/sendmsg.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.0"
},
{
"lessThan": "6.0",
"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.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\nrxrpc: Fix update of call-\u003etx_pending without holding lock\n\nCurrently, rxrpc_send_data() updates call-\u003etx_pending just before it\nreturns - but it won\u0027t be holding the call-\u003euser_mutex when it does this if\na wait was interrupted by a signal. This would allow a parallel sendmsg()\nto race.\n\nFurther, both the callers of rxrpc_send_data() call it with the lock held,\nand then it returns an indication through the parameter list to say whether\nit has dropped the lock or not - after which the callers both just drop the\nlock if it\u0027s still held.\n\nFix this by:\n\n (1) Moving the release of call-\u003euser_mutex down into rxrpc_send_data() and\n get rid of the indicator parameter. This makes it easier to see where\n the lock is held.\n\n (2) After waiting, if the attempt to reacquire the mutex is interrupted,\n just return directly there rather than going to out_unlock\n\n (3) Restricting the txb variable to inside the buffering loop and leaving\n -\u003etx_pending set until we\u0027ve queued the buffer.\n\nNote that there\u0027s a slight change in behaviour in that wait_for_space\nfailure now doesn\u0027t check for completion because it doesn\u0027t hold the call\nuser_mutex. The caller, however, should re-issue the send and pick up any\nerror at a second attempt."
}
],
"id": "CVE-2026-99350",
"lastModified": "2026-11-19T15:17:46.313",
"metrics": {},
"published": "2026-11-19T15:17:46.313",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/35f7a69391ca0819d04ca6db3c2355848d633e16"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7801c42c3bb737cfb06194a383873fcad8daacf5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/965456110cf6952cc4eec80761171503e6e424df"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ec98e8bdbde85e2dd2d43570e25b52bdfac1735b"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-19T16:46:18+00:00",
"cve": "CVE-2026-99350",
"id": "CVE-2026-99350",
"initial_release_date": "2026-11-19T14:22:10.838000+00:00",
"product_status:known_affected": "113",
"product_status:known_not_affected": "91",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service via race condition in rxrpc",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99350.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.