RDMA/efa: Fix PBL chunk length computation
- 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.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 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
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/efa: Fix PBL chunk length computation On register MR, when creating the PBL, if it's an indirect PBL we create a chunk list to hold the PBL pages pointers. Each chunk is 4KB in size and can hold 510 addresses (EFA_PTRS_PER_CHUNK) and has a 12-byte control buffer at the end of it holding the next chunk's pointer and its length. If the PBL number of pages is a multiple of EFA_PTRS_PER_CHUNK, the calculated last chunk length is wrongly computed as 0, even though that chunk is fully populated with 510 real page pointers. This wrong length is used both to DMA map the chunk and is propagated to the device, causing the device to see the chunk as empty and reject the memory registration. Fix the calculation so it will be performed only if the number of pages isn't a multiple of EFA_PTRS_PER_CHUNK, if it is, its already handled in the above loop correctly. Also prevent out-of-bounds reach in the chunks array in such scenario.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 665cd418b8561a099c3854443f8ad8ae751b72a0; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 932e5684906a090644a9061fae2d254041c3b8f2; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 489b28f2377afa70c18c45b06a6387f3d39bb123; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in aadf3f9b5edb7f0a77e9172b237d2e07c754829c; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 3982714e15512b83115897806dacc94899683420; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in da7805f0211af19968584e621074f253ac07dba7; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 1d4b5902773475fc97151379b7e5f09cad0fa57b; From 40909f664d279765af430acc5db348a0b71c9b0a · fixed in 229b42d7450c1cf96f45ec39ebb69211b06bc036
- Linux Linux
5.2
- KernelLinux
From 5.2.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/665cd418b8561a099c3854443f8ad8ae751b72a0
- stable/c/932e5684906a090644a9061fae2d254041c3b8f2
- stable/c/489b28f2377afa70c18c45b06a6387f3d39bb123
- stable/c/aadf3f9b5edb7f0a77e9172b237d2e07c754829c
- stable/c/3982714e15512b83115897806dacc94899683420
- stable/c/da7805f0211af19968584e621074f253ac07dba7
- stable/c/1d4b5902773475fc97151379b7e5f09cad0fa57b
- stable/c/229b42d7450c1cf96f45ec39ebb69211b06bc036