CVE-2026-99517: Linux kernel · nvmet: fix use-after-free of the old registrant in nvmet_pr_preempt()
Source GCVE Database
Not known to be exploited · fixed in fd7843365a9e73f6ee32c30487c21cb62b84c0a2 : patch Linux kernel soon.
Data as of 19 Nov 2026, 16:49 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fd7843365a9e73f6ee32c30487c21cb62b84c0a2, f316aa7f018840523939183425394931b373e4d7, 506c066da8fb2cef32210ca84439c7bb9855504f
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to fd7843365a9e73f6ee32c30487c21cb62b84c0a2, f316aa7f018840523939183425394931b373e4d7 or 506c066da8fb2cef32210ca84439c7bb9855504f.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that include this patch. Since this is a kernel-level issue, upgrading to a fixed kernel version is the recommended mitigation.
Description
A use-after-free vulnerability in the Linux kernel's nvmet_pr_preempt() function was identified and fixed. The flaw involves reading freed memory when handling reservation preemption notifications, potentially causing memory corruption or kernel instability. The issue arises because the old registrant is freed asynchronously but accessed afterward without proper synchronization. The fix involves passing the host ID of the controller that sent the command instead of the freed registrant to avoid accessing freed memory.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99517 (opens in a new tab)
- git.kernel.org/stable/c/506c066da8fb2cef32210ca84439c7bb9855504f (opens in a new tab)
- git.kernel.org/stable/c/f316aa7f018840523939183425394931b373e4d7 (opens in a new tab)
- git.kernel.org/stable/c/fd7843365a9e73f6ee32c30487c21cb62b84c0a2 (opens in a new tab)