{"id":"CVE-2026-99019","title":"scsi: ch: Do not keep references to data transfer element devices","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ch: Do not keep references to data transfer element devices\n\nch_readconfig() looks up the scsi_device of every data transfer element\nwhose SCSI id the changer rep…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < ec6ecab1b7577ae555ee6b81480814d123dd9ec0","Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db","Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < a34a230ccea1b8b667ae59dca11295a2c8f81738","Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < 1d35a17f1c2ed4154731895694a1a3557f0da766","Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < 27c0f718d3b3c99e6d315308e95d987d0382a8a8","Linux 2.6.13"],"published":"2026-10-23","updated":"2026-10-23","sourceUpdated":"2026-10-23T12:20:55.832Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-99019","references":[{"url":"https://git.kernel.org/stable/c/ec6ecab1b7577ae555ee6b81480814d123dd9ec0"},{"url":"https://git.kernel.org/stable/c/cef2cedb6f7a394b278775b3d6ffb9b20ecd61db"},{"url":"https://git.kernel.org/stable/c/a34a230ccea1b8b667ae59dca11295a2c8f81738"},{"url":"https://git.kernel.org/stable/c/1d35a17f1c2ed4154731895694a1a3557f0da766"},{"url":"https://git.kernel.org/stable/c/27c0f718d3b3c99e6d315308e95d987d0382a8a8"}],"tags":["cve.org"],"ingestedAt":"2026-10-23T13:24:55.536Z","slug":"CVE-2026-99019","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ch: Do not keep references to data transfer element devices\n\nch_readconfig() looks up the scsi_device of every data transfer element\nwhose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in\nch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops\nit: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere\nelse - it only supplies the vendor, model and revision printed in the same\nloop.\n\nOnce such a drive is removed, its scsi_device can never be released. It\nstays on the host's device list at its address, so a new device there is\nrefused by anything that walks the list - target_core_pscsi reports\n\"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module\ncan no longer be unloaded. Only a reboot recovers.\n\nIt shows with any changer that reports its drives' ids; with the mhvtl\nvirtual library (IBM 3573-TL personality), each create and remove of a\nlibrary with four drives leaves four references behind, counted by the\nmodule's use count in lsmod. With ch not bound the count is unchanged, and\nwith this patch applied it is unchanged too.\n\nDrop the reference as soon as the name has been printed, and remove the now\nunused dt[] array. That also removes the array leaked when ch_probe() fails\nafter ch_readconfig().\n\nThe same leak was reported with an RFC patch in 2022, which was not merged.\n\n## Affected\n\n- `Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < ec6ecab1b7577ae555ee6b81480814d123dd9ec0`\n- `Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db`\n- `Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < a34a230ccea1b8b667ae59dca11295a2c8f81738`\n- `Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < 1d35a17f1c2ed4154731895694a1a3557f0da766`\n- `Linux >= daa6eda65a53e5addf86c6bc829129ff51b08bda < 27c0f718d3b3c99e6d315308e95d987d0382a8a8`\n- `Linux 2.6.13`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}