CVE-2026-74470
scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write resp_report_zones() sizes the reply buffer from the CDB allocation length. The v3 fix rounds alloc_len up with ALIGN() before deriving the descriptor count: rep_max_zones = (ALIGN((u64)alloc_len, RZONES_DESC_HD) - RZONES_DESC_HD) >> ilog2(RZONES_DESC_HD); arr_len = (u64)RZONES_DESC_HD * (rep_max_zones + 1); For alloc_len in 0xFFFFFFC1..0xFFFFFFFF, ALIGN() rounds up to 0x100000000, so arr_len is 4 GB. On 32-bit, kzalloc()'s size_t is 32-bit and truncates 0x100000000 to 0; kzalloc(0) returns ZERO_SIZE_PTR, which passes the !arr check, and desc = arr + 64 is then dereferenced in the loop -> out-of-bounds write / panic. Clamp rep_max_zones to devip->nr_zones. The loop already stops at sdebug_capacity (after nr_zones zones), so a report can never hold more than nr_zones descriptors; the clamp does not change the report, it only bounds arr_len to (nr_zones + 1) * RZONES_DESC_HD, a real device property that can never reach 0x100000000.
INFO
Published Date :
Aug. 15, 2026, 1:17 p.m.
Last Modified :
Aug. 15, 2026, 1:17 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-74470
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the resolved version.
- Apply the specific scsi_debug fix.
- Verify the kernel version after patching.
- Reboot the system if necessary.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-74470.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-74470 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-74470
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-74470 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-74470 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 15, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '7db0e0c8190a086ef92ce5bb960836cde49540aa', 'lessThan': '49e5b25a0b74dbac595f122e5608fdce2918cc4e', 'versionType': 'git'}, {'status': 'affected', 'version': '7db0e0c8190a086ef92ce5bb960836cde49540aa', 'lessThan': '495058429ca55ab7fcc21977b63b92907ad68066', 'versionType': 'git'}, {'status': 'affected', 'version': '7db0e0c8190a086ef92ce5bb960836cde49540aa', 'lessThan': '2047ed09bf13453b7d6f9431b112ec07984dd69b', 'versionType': 'git'}, {'status': 'affected', 'version': '7db0e0c8190a086ef92ce5bb960836cde49540aa', 'lessThan': 'd6e6da6bc3b53231fac77ffab428da8173ee729c', 'versionType': 'git'}, {'status': 'affected', 'version': '7db0e0c8190a086ef92ce5bb960836cde49540aa', 'lessThan': '93dde0bf2f39a0f9f57fd610aa3201ce5b753433', 'versionType': 'git'}, {'status': 'affected', 'version': 'c4d2d7c935a4ad20e8e726ca10499cefe4537103', 'versionType': 'git'}, {'status': 'affected', 'version': 'ebacb44cb2042b90951140eda806bedad23ef554', 'versionType': 'git'}, {'status': 'affected', 'version': '5.10.85', 'lessThan': '5.11', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.15.8', 'lessThan': '5.16', 'versionType': 'semver'}], 'programFiles': ['drivers/scsi/scsi_debug.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.16'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.16', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.151', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.103', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.44', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.8', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc6', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/scsi/scsi_debug.c'], 'defaultStatus': 'affected'}] Added Description In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write resp_report_zones() sizes the reply buffer from the CDB allocation length. The v3 fix rounds alloc_len up with ALIGN() before deriving the descriptor count: rep_max_zones = (ALIGN((u64)alloc_len, RZONES_DESC_HD) - RZONES_DESC_HD) >> ilog2(RZONES_DESC_HD); arr_len = (u64)RZONES_DESC_HD * (rep_max_zones + 1); For alloc_len in 0xFFFFFFC1..0xFFFFFFFF, ALIGN() rounds up to 0x100000000, so arr_len is 4 GB. On 32-bit, kzalloc()'s size_t is 32-bit and truncates 0x100000000 to 0; kzalloc(0) returns ZERO_SIZE_PTR, which passes the !arr check, and desc = arr + 64 is then dereferenced in the loop -> out-of-bounds write / panic. Clamp rep_max_zones to devip->nr_zones. The loop already stops at sdebug_capacity (after nr_zones zones), so a report can never hold more than nr_zones descriptors; the clamp does not change the report, it only bounds arr_len to (nr_zones + 1) * RZONES_DESC_HD, a real device property that can never reach 0x100000000. Added Reference https://git.kernel.org/stable/c/2047ed09bf13453b7d6f9431b112ec07984dd69b Added Reference https://git.kernel.org/stable/c/495058429ca55ab7fcc21977b63b92907ad68066 Added Reference https://git.kernel.org/stable/c/49e5b25a0b74dbac595f122e5608fdce2918cc4e Added Reference https://git.kernel.org/stable/c/93dde0bf2f39a0f9f57fd610aa3201ce5b753433 Added Reference https://git.kernel.org/stable/c/d6e6da6bc3b53231fac77ffab428da8173ee729c