Improper Update of Reference Count Affecting bpftool6.12-debuginfo package, versions <1:6.12.114-139.210.amzn2023
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-BPFTOOL612DEBUGINFO-22396347
- published10 Nov 2026
- disclosed23 Oct 2026
Introduced: 23 Oct 2026
NewCVE-2026-99019 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 bpftool6.12-debuginfo to version 1:6.12.114-139.210.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3402.
NVD Description
Note: Versions mentioned in the description apply only to the upstream bpftool6.12-debuginfo package and not the bpftool6.12-debuginfo package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
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.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-99019
- https://git.kernel.org/stable/c/1d35a17f1c2ed4154731895694a1a3557f0da766
- https://git.kernel.org/stable/c/27c0f718d3b3c99e6d315308e95d987d0382a8a8
- https://git.kernel.org/stable/c/a34a230ccea1b8b667ae59dca11295a2c8f81738
- https://git.kernel.org/stable/c/cef2cedb6f7a394b278775b3d6ffb9b20ecd61db
- https://git.kernel.org/stable/c/ec6ecab1b7577ae555ee6b81480814d123dd9ec0
- https://git.kernel.org/stable/c/03287b176e8f7cc5680a7053e2d53bd5cb05d80c
- https://git.kernel.org/stable/c/72ad7b08ffd5d9495715db0d74ce325a485f1b52
- https://git.kernel.org/stable/c/7412c6fb671dda9776deebb283daf0bb2f1b48e5