nvmet-rdma: handle inline data with a nonzero offset
- 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.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 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: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: handle inline data with a nonzero offset nvmet_rdma_use_inline_sg() maps the host-controlled inline data offset into the per-command inline scatterlist. The bounds check admits any offset with off + len <= inline_data_size, but the mapping still assumes the data begins in the first inline page: sg->offset = off; sg->length = min_t(int, len, PAGE_SIZE - off); When a port is configured with inline_data_size > PAGE_SIZE (settable up to max(SZ_16K, PAGE_SIZE)), an offset in (PAGE_SIZE, inline_data_size] makes "PAGE_SIZE - off" underflow, so sg->length is set to ~4 GiB and the block backend reads far past the first inline page. num_pages(len) also ignores the offset, so an in-bounds offset whose [off, off+len) span crosses a page boundary under-counts the scatterlist. Map the offset properly: split it into a page index and an in-page offset, start the scatterlist at that page, and size the page count from page_off + len. Because the request scatterlist may now start at inline_sg[page_idx] rather than inline_sg[0], generalize the inline-SGL identity test in nvmet_rdma_release_rsp() to a range test; otherwise the persistent inline scatterlist is mistaken for an allocated one and nvmet_req_free_sgls() frees an inline page (and warns in free_large_kmalloc()).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in c2106ba1b14d644a5203bea1a50dbe25dcad713c; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in bf8bcc1c137d54a62a428b00051fdbb13660673b; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 11401371152b228448a41d79c6de1c938f93049a; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 7c96581169c9d9a7d0726e554313acfbead6141c; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 42a8ea3acd883f4f210d9e54e0975b1e2292b529; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 2944113ad5fbcdf5d349d857c03d2a44b6de75b8; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 98bcdfa619150b2f41fa15bac140dbaf2584ad05; From 0d5ee2b2ab4f6776c361bc975c2323bc8b5cf349 · fixed in 48c0162f647bb47e6084ffbc71b8f213f5e2f4f8
- Linux Linux
4.19
- KernelLinux
From 4.19.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/c2106ba1b14d644a5203bea1a50dbe25dcad713c
- stable/c/bf8bcc1c137d54a62a428b00051fdbb13660673b
- stable/c/11401371152b228448a41d79c6de1c938f93049a
- stable/c/7c96581169c9d9a7d0726e554313acfbead6141c
- stable/c/42a8ea3acd883f4f210d9e54e0975b1e2292b529
- stable/c/2944113ad5fbcdf5d349d857c03d2a44b6de75b8
- stable/c/98bcdfa619150b2f41fa15bac140dbaf2584ad05
- stable/c/48c0162f647bb47e6084ffbc71b8f213f5e2f4f8