CVE-2026-23087: Linux kernel · scsi: xen: scsiback: Fix potential memory leak in scsiback_remove()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f86264ec0e2b102fcd49bf3e4f32fee669d482fc : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in f86264ec0e2b102fcd49bf3e4f32fee669d482fc, a8bb3ec8d85951a56af0a72d93ccbc2aee42eef9, 901a5f309daba412e2a30364d7ec1492fa11c32c +4
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: xen: scsiback: Fix potential memory leak in scsiback_remove() Memory allocated for struct vscsiblk_info in scsiback_probe() is not freed in scsiback_remove() leading to potential memory leaks on remove, as well as in the scsiback_probe() error paths. Fix that by freeing it in scsiback_remove().
References
- git.kernel.org/stable/c/a8bb3ec8d85951a56af0a72d93ccbc2aee42eef9 (opens in a new tab)
- git.kernel.org/stable/c/427b0fb30ddec3bad05dcd73b00718f98c7026d2 (opens in a new tab)
- git.kernel.org/stable/c/4a975c72429b050c234405668b742cdecc11548e (opens in a new tab)
- git.kernel.org/stable/c/f86264ec0e2b102fcd49bf3e4f32fee669d482fc (opens in a new tab)
- git.kernel.org/stable/c/32e52b56056daf0f0881fd9254706acf25b4be97 (opens in a new tab)
- git.kernel.org/stable/c/24c441f0e24da175d7912095663f526ac480dc4f (opens in a new tab)
- git.kernel.org/stable/c/901a5f309daba412e2a30364d7ec1492fa11c32c (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)