Answer in brief
CVE-2026-99019 records a Unknown severity vulnerability in scsi: ch: Do not keep references to data transfer element devices. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=daa6eda65a53e5addf86c6bc829129ff51b08bda <ec6ecab1b7577ae555ee6b81480814d123dd9ec0 || >=daa6eda65a53e5addf86c6bc829129ff51b08bda <cef2cedb6f7a394b278775b3d6ffb9b20ecd61db || >=daa6eda65a53e5addf86c6bc829129ff51b08bda <a34a230ccea1b8b667ae59dca11295a2c8f81738 || >=daa6eda65a53e5addf86c6bc829129ff51b08bda <1d35a17f1c2ed4154731895694a1a3557f0da766 || >=daa6eda65a53e5addf86c6bc829129ff51b08bda <27c0f718d3b3c99e6d315308e95d987d0382a8a8 | ec6ecab1b7577ae555ee6b81480814d123dd9ec0, cef2cedb6f7a394b278775b3d6ffb9b20ecd61db, a34a230ccea1b8b667ae59dca11295a2c8f81738, 1d35a17f1c2ed4154731895694a1a3557f0da766, 27c0f718d3b3c99e6d315308e95d987d0382a8a8 |
| Linux/Linuxgeneric | 2.6.13 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.