ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-99019

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

Published Oct 23, 2026 · catalog updated Oct 28, 2026 · Linux Linux

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-99019. EPSS is 0.18%. Act only if a listed version of Linux Linux is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.18%
Remediation
Advisory link
Affected products
Ubuntu:16.04:LTS linux-hwe-edge · Ubuntu:Pro:14.04:LTS linux · Ubuntu:Pro:14.04:LTS linux-aws · Ubuntu:Pro:14.04:LTS linux-azure · Ubuntu:Pro:14.04:LTS linux-lts-xenial · Ubuntu:Pro:16.04:LTS linux

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Ubuntu:16.04:LTS linux-hwe-edge4.8.0-28.30~16.04.1, 4.8.0-30.32~16.04.1, 4.8.0-32.34~16.04.1
  • Ubuntu:Pro:14.04:LTS linux3.11.0-12.19, 3.12.0-1.3, 3.12.0-2.5
  • Ubuntu:Pro:14.04:LTS linux-aws4.4.0-1002.2, 4.4.0-1003.3, 4.4.0-1005.5
  • Ubuntu:Pro:14.04:LTS linux-azure4.15.0-1023.24~14.04.1, 4.15.0-1030.31~14.04.1, 4.15.0-1031.32~14.04.1
  • Ubuntu:Pro:14.04:LTS linux-lts-xenial4.4.0-13.29~14.04.1, 4.4.0-14.30~14.04.2, 4.4.0-15.31~14.04.1
  • Ubuntu:Pro:16.04:LTS linux4.2.0-16.19, 4.2.0-17.21, 4.2.0-19.23
  • Ubuntu:Pro:16.04:LTS linux-aws4.4.0-1001.10, 4.4.0-1003.12, 4.4.0-1004.13
  • Ubuntu:Pro:16.04:LTS linux-aws-hwe4.15.0-1030.31~16.04.1, 4.15.0-1031.33~16.04.1, 4.15.0-1032.34~16.04.1
  • Ubuntu:Pro:16.04:LTS linux-azure4.11.0-1009.9, 4.11.0-1011.11, 4.11.0-1013.13
  • Ubuntu:Pro:16.04:LTS linux-gcp4.10.0-1004.4, 4.10.0-1006.6, 4.10.0-1007.7
  • Ubuntu:Pro:16.04:LTS linux-hwe4.8.0-36.36~16.04.1, 4.8.0-39.42~16.04.1, 4.8.0-41.44~16.04.1
  • Ubuntu:Pro:16.04:LTS linux-kvm4.4.0-1004.9, 4.4.0-1007.12, 4.4.0-1008.13
  • vendor Linux Linuxversion unspecified

How to fix CVE-2026-99019

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-99019. EPSS is 0.18%. Act only if a listed version of Linux Linux is installed.

Which versions are affected?

Compare what you have installed with 4.8.0-28.30~16.04.1, 4.8.0-30.32~16.04.1, 4.8.0-32.34~16.04.1, 3.11.0-12.19, 3.12.0-1.3, 3.12.0-2.5, 4.4.0-1002.2, 4.4.0-1003.3, 4.4.0-1005.5, 4.15.0-1023.24~14.04.1, 4.15.0-1030.31~14.04.1, 4.15.0-1031.32~14.04.1, 4.4.0-13.29~14.04.1, 4.4.0-14.30~14.04.2, 4.4.0-15.31~14.04.1, 4.2.0-16.19, 4.2.0-17.21, 4.2.0-19.23. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.18%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Ubuntu security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 23, 2026 · Tenable CVE Database

    Detected

    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().

  2. Oct 23, 2026 · CVE.org

    Updated

    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().

  3. Oct 28, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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().

Sources

  • CVE.orgVulnerability recordCVE-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

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-99019

    30-day exploitation probability 0.18%

    first.org
  • OpenSSF OSV / OSV ScannerPackage advisoryUBUNTU-CVE-2026-99019
    osv.dev
  • Tenable CVE DatabaseVulnerability recordCVE-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().

    tenable.com

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 31, 2026
  • OpenSSF OSV / OSV ScannerOct 28, 2026
  • CVE.orgOct 25, 2026
  • Tenable CVE DatabaseOct 23, 2026