CVE-2026-99019

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

State
Published
Severity
Not scored
Published
Oct 23, 2026
Updated
Oct 30, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before 7412c6fb671dda9776deebb283daf0bb2f1b48e5Affected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before 03287b176e8f7cc5680a7053e2d53bd5cb05d80cAffected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before 72ad7b08ffd5d9495715db0d74ce325a485f1b52Affected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before ec6ecab1b7577ae555ee6b81480814d123dd9ec0Affected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before cef2cedb6f7a394b278775b3d6ffb9b20ecd61dbAffected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before a34a230ccea1b8b667ae59dca11295a2c8f81738Affected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before 1d35a17f1c2ed4154731895694a1a3557f0da766Affected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda to before 27c0f718d3b3c99e6d315308e95d987d0382a8a8Affected
LinuxLinux
  • 2.6.13Affected
  • before 2.6.13Not affected
  • 5.10.273 through 5.10.*Not affected
  • 5.15.224 through 5.15.*Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.58 through 6.18.*Not affected
  • 7.2.11 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.