CVE-2026-99019

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

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.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.185% likely to be exploited in the next 30 days, higher than 8.189% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding 7412c6fb671dda9776deebb283daf0bb2f1b48e5 (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding 03287b176e8f7cc5680a7053e2d53bd5cb05d80c (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding 72ad7b08ffd5d9495715db0d74ce325a485f1b52 (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding ec6ecab1b7577ae555ee6b81480814d123dd9ec0 (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding cef2cedb6f7a394b278775b3d6ffb9b20ecd61db (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding a34a230ccea1b8b667ae59dca11295a2c8f81738 (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding 1d35a17f1c2ed4154731895694a1a3557f0da766 (affected)
  • daa6eda65a53e5addf86c6bc829129ff51b08bda up to but excluding 27c0f718d3b3c99e6d315308e95d987d0382a8a8 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.13 (affected)
  • 0 up to but excluding 2.6.13 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.58 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References