◆ CVE Hub

CVE-2026-99019

scsi: ch: Do not keep references to data transfer element devices

Published
2026-10-23
Last modified
2026-10-23
CNA
Linux
NVD status
Received

Fetching some sources has been requested. Reload in about a minute to see them.

CVSS v3.1 (listed by NVD)
—
Not scored
CVSS v4.0 (listed by NVD)
—
Not scored
CVSS (listed by CVE.org)
—
Not scored
EPSS exploit probability
0.2%
Percentile 10.5%
as of 2026-10-24
CISA KEV
—
Not listed

Description

NVD

In the Linux kernel, the following vulnerability has been resolved: scsi: ch: Do not keep references to data transfer element devices ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop. Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports "scsi_device_get() failed for H:C:T:L" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers. It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too. Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig(). The same leak was reported with an RFC patch in 2022, which was not merged.

Affected products and packages

CNA (CVE.org)

VendorProductVersions
LinuxLinux
affected: daa6eda65a53e5addf86c6bc829129ff51b08bda … < ec6ecab1b7577ae555ee6b81480814d123dd9ec0
affected: daa6eda65a53e5addf86c6bc829129ff51b08bda … < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db
affected: daa6eda65a53e5addf86c6bc829129ff51b08bda … < a34a230ccea1b8b667ae59dca11295a2c8f81738
affected: daa6eda65a53e5addf86c6bc829129ff51b08bda … < 1d35a17f1c2ed4154731895694a1a3557f0da766
affected: daa6eda65a53e5addf86c6bc829129ff51b08bda … < 27c0f718d3b3c99e6d315308e95d987d0382a8a8
default: unaffected
LinuxLinux
affected: 2.6.13
unaffected: 0 … < 2.6.13
unaffected: 6.6.160 … <= 6.6.*
unaffected: 6.12.114 … <= 6.12.*
unaffected: 6.18.58 … <= 6.18.*
unaffected: 7.2.11 … <= 7.2.*
unaffected: 7.3 … <= *
default: affected

Open-source packages (GitHub Advisory / OSV)

scsi: ch: Do not keep references to data transfer element devices

EcosystemPackageAffected versionsFixed in
>= daa6eda65a53e5addf86c6bc829129ff51b08bda, < ec6ecab1b7577ae555ee6b81480814d123dd9ec0; < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db; < a34a230ccea1b8b667ae59dca11295a2c8f81738; < 1d35a17f1c2ed4154731895694a1a3557f0da766; < 27c0f718d3b3c99e6d315308e95d987d0382a8a8ec6ecab1b7577ae555ee6b81480814d123dd9ec0, cef2cedb6f7a394b278775b3d6ffb9b20ecd61db, a34a230ccea1b8b667ae59dca11295a2c8f81738, 1d35a17f1c2ed4154731895694a1a3557f0da766, 27c0f718d3b3c99e6d315308e95d987d0382a8a8
LinuxKernel>= 2.6.13, < 6.6.160; >= 6.7.0, < 6.12.114; >= 6.13.0, < 6.18.58; >= 6.19.0, < 7.2.116.6.160, 6.12.114, 6.18.58, 7.2.11

Linux distribution status

Red Hat ↗ Fetching

Debian ↗

ReleasePackageStatusFixed version / notes
bookwormlinuxopen not yet assigned
forkylinuxresolved not yet assigned7.2.11-1
sidlinuxresolved not yet assigned7.2.11-1
trixielinuxopen not yet assigned

Ubuntu ↗ Fetching

References (8)