scsi: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done()
- 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 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 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: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done() A malicious or compromised VIO server can return a num_written value in the discover targets MAD response that exceeds max_targets. This value is stored directly in vhost->num_targets without validation, and is then used as the loop bound in ibmvfc_alloc_targets() to index into disc_buf[], which is only allocated for max_targets entries. Indices at or beyond max_targets access kernel memory outside the DMA-coherent allocation. The out-of-bounds data is subsequently embedded in Implicit Logout and PLOGI MADs that are sent back to the VIO server, leaking kernel memory. Fix by clamping num_written to max_targets before storing it.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in d842348f8a00d5b1d7358f207eb34ffcf5b16df3; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in a007246cb6c9ebdc93dafbf63cc2d43d98f402cc; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in 394a1cac3c12fdd7d77f19ccfd222ab5ff87ef89; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in 4ed727e35b0ab17d3eeeb1e8023768396e2be161; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in d1466bf991b2343cf2ba8336e440c8faf3cbb780; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in 786f10b1966e485046839f992e89f2c18cbd1983; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in bae4df0a643fa7f84663473aa3082a9c2ed139db; From 072b91f9c6510d0ec4a49d07dbc318760c7da7b3 · fixed in 61d099ac4a7a8fb11ebdb6e2ec8d77f38e77362f
- Linux Linux
2.6.27
- KernelLinux
From 2.6.27 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.168; From 6.2.0 · fixed in 6.6.131; From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11
References 8
git.kernel.org
- stable/c/d842348f8a00d5b1d7358f207eb34ffcf5b16df3
- stable/c/a007246cb6c9ebdc93dafbf63cc2d43d98f402cc
- stable/c/394a1cac3c12fdd7d77f19ccfd222ab5ff87ef89
- stable/c/4ed727e35b0ab17d3eeeb1e8023768396e2be161
- stable/c/d1466bf991b2343cf2ba8336e440c8faf3cbb780
- stable/c/786f10b1966e485046839f992e89f2c18cbd1983
- stable/c/bae4df0a643fa7f84663473aa3082a9c2ed139db
- stable/c/61d099ac4a7a8fb11ebdb6e2ec8d77f38e77362f