GHSA-P68W-HQQQ-M236
Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31In the Linux kernel, the following vulnerability has been resolved:
lockd: Fix use-after-free in nlmsvc_retry_blocked
nlmsvc_retry_blocked() examines the block at the head of nlm_blocked under nlm_blocked_lock, then releases the lock before calling nlmsvc_grant_blocked() or retry_deferred_block(). The nlm_blocked list reference is all that keeps the block alive across that window. nlmsvc_grant_blocked() does take one of its own, but not until after the lock has been dropped. Unmounting the nfsd filesystem while a lock request is still blocked reaches nlmsvc_traverse_blocks(), which drops the list reference and frees the block along with the nlm_rqst hanging off it.
BUG: KASAN: slab-use-after-free in nlm_async_call+0xd6/0x230 Read of size 8 at addr ffff88811b04c808 by task lockd/8377 nlm_async_call+0xd6/0x230 nlmsvc_retry_blocked+0x61c/0x800 lockd+0x144/0x1c0 Freed by task 8392: nlmsvc_release_block+0x231/0x290 nlmsvc_traverse_blocks+0x139/0x1b0 nlm_traverse_files+0x1aa/0xa00 nlmsvc_free_host_resources+0x12/0x60 nlm_shutdown_hosts_net+0x127/0x280 lockd_down+0xd5/0x1c0
Take a reference before releasing nlm_blocked_lock and drop it once the retry has run.
{
"affected": [],
"aliases": [
"CVE-2026-99513"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T15:18:06Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nlockd: Fix use-after-free in nlmsvc_retry_blocked\n\nnlmsvc_retry_blocked() examines the block at the head of nlm_blocked\nunder nlm_blocked_lock, then releases the lock before calling\nnlmsvc_grant_blocked() or retry_deferred_block(). The nlm_blocked list\nreference is all that keeps the block alive across that window.\nnlmsvc_grant_blocked() does take one of its own, but not until after\nthe lock has been dropped. Unmounting the nfsd filesystem while a lock\nrequest is still blocked reaches nlmsvc_traverse_blocks(), which drops\nthe list reference and frees the block along with the nlm_rqst hanging\noff it.\n\n BUG: KASAN: slab-use-after-free in nlm_async_call+0xd6/0x230\n Read of size 8 at addr ffff88811b04c808 by task lockd/8377\n nlm_async_call+0xd6/0x230\n nlmsvc_retry_blocked+0x61c/0x800\n lockd+0x144/0x1c0\n Freed by task 8392:\n nlmsvc_release_block+0x231/0x290\n nlmsvc_traverse_blocks+0x139/0x1b0\n nlm_traverse_files+0x1aa/0xa00\n nlmsvc_free_host_resources+0x12/0x60\n nlm_shutdown_hosts_net+0x127/0x280\n lockd_down+0xd5/0x1c0\n\nTake a reference before releasing nlm_blocked_lock and drop it once\nthe retry has run.",
"id": "GHSA-p68w-hqqq-m236",
"modified": "2026-11-19T15:31:27Z",
"published": "2026-11-19T15:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99513"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/25d0baa6adb4a0b3f6889d42033ce8df3232bea7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6506c27da6756c0c7590ef60774ee5d35f6a4100"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/70825b251e5f7855fd7bd93afc0b698154e00e70"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f5b7634f0f213299a07b461fb10385c8639a4ab8"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.