Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99019scsi: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < 7412c6fb671dda9776deebb283daf0bb2f1b48e5
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < 03287b176e8f7cc5680a7053e2d53bd5cb05d80c
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < 72ad7b08ffd5d9495715db0d74ce325a485f1b52
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < ec6ecab1b7577ae555ee6b81480814d123dd9ec0
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < cef2cedb6f7a394b278775b3d6ffb9b20ecd61db
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < a34a230ccea1b8b667ae59dca11295a2c8f81738
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < 1d35a17f1c2ed4154731895694a1a3557f0da766
    • affected daa6eda65a53e5addf86c6bc829129ff51b08bda – < 27c0f718d3b3c99e6d315308e95d987d0382a8a8
  • Linux · Linux

    • affected 2.6.13
    • unaffected < 2.6.13
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.58 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99019 badge
[![CVE-2026-99019](https://cveledger.app/badge/CVE-2026-99019.svg)](https://cveledger.app/cve/CVE-2026-99019)

Record last updated .