CVE-2026-99019: Linux Vulnerability

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.

Metrics

EPSS Probability

0.18%

7.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= daa6eda65a53e5addf86c6bc829129ff51b08bda, < 7412c6fb671dda9776deebb283daf0bb2f1b48e5; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < 03287b176e8f7cc5680a7053e2d53bd5cb05d80c; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < 72ad7b08ffd5d9495715db0d74ce325a485f1b52; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < ec6ecab1b7577ae555ee6b81480814d123dd9ec0; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < a34a230ccea1b8b667ae59dca11295a2c8f81738; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < 1d35a17f1c2ed4154731895694a1a3557f0da766; >= daa6eda65a53e5addf86c6bc829129ff51b08bda, < 27c0f718d3b3c99e6d315308e95d987d0382a8a8
Linux	Linux	2.6.13

References

Timeline

Published: Oct 23, 2026
Last Modified: Oct 30, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-99019?

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.

How severe is CVE-2026-99019?

Severity scoring for CVE-2026-99019 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.

How do I fix CVE-2026-99019?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →