scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory There is a potential out-of-bounds access when using test_bit() on a single word. The test_bit() and set_bit() functions operate on long values, and when testing or setting a single word, they can exceed the word boundary. KASAN detects this issue and produces a dump: BUG: KASAN: slab-out-of-bounds in _scsih_add_device.constprop.0 (./arch/x86/include/asm/bitops.h:60 ./include/asm-generic/bitops/instrumented-atomic.h:29 drivers/scsi/mpt3sas/mpt3sas_scsih.c:7331) mpt3sas Write of size 8 at addr ffff8881d26e3c60 by task kworker/u1536:2/2965 For full log, please look at [1]. Make the allocation at least the size of sizeof(unsigned long) so that set_bit() and test_bit() have sufficient room for read/write operations without overwriting unallocated memory. [1] Link: https://lore.kernel.org/all/ZkNcALr3W3KGYYJG@gmail.com/
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From c696f7b83edeac804e898952058089143f49ca0a · fixed in e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 19649e49a6df07cd2e03e0a11396fd3a99485ec2; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 521f333e644c4246ca04a4fc4772edc53dd2a801; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 46bab2bcd771e725ff5ca3a68ba68cfeac45676c; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 9079338c5a0d1f1fee34fb1c9e99b754efe414c5; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 18abb5db0aa9b2d48f7037a88b41af2eef821674; From c696f7b83edeac804e898952058089143f49ca0a · fixed in 4254dfeda82f20844299dca6c38cbffcfd499f41
- Linux Linux
4.10
- KernelLinux
From 4.10.0 · fixed in 4.19.317; From 4.20.0 · fixed in 5.4.279; From 5.5.0 · fixed in 5.10.221; From 5.11.0 · fixed in 5.15.162; From 5.16.0 · fixed in 6.1.95; From 6.2.0 · fixed in 6.6.35; From 6.7.0 · fixed in 6.9.6
References 8
git.kernel.org
- stable/c/e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee
- stable/c/19649e49a6df07cd2e03e0a11396fd3a99485ec2
- stable/c/0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16
- stable/c/521f333e644c4246ca04a4fc4772edc53dd2a801
- stable/c/46bab2bcd771e725ff5ca3a68ba68cfeac45676c
- stable/c/9079338c5a0d1f1fee34fb1c9e99b754efe414c5
- stable/c/18abb5db0aa9b2d48f7037a88b41af2eef821674
- stable/c/4254dfeda82f20844299dca6c38cbffcfd499f41