Strix
64.5K

CVE-2026-93264

Unknown

Last modified

CVE-2026-93264 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 40909f664d279765af430acc5db348a0b71c9b0a, < 665cd418b8561a099c3854443f8ad8ae751b72a0; >= 40909f664d279765af430acc5db348a0b71c9b0a, < 932e5684906a090644a9061fae2d254041c3b8f2; >= 40909f664d279765af430acc5db348a0b71c9b0a, < 489b28f2377afa70c18c45b06a6387f3d39bb123; >= 40909f664d279765af430acc5db348a0b71c9b0a, < aadf3f9b5edb7f0a77e9172b237d2e07c754829c; >= 40909f664d279765af430acc5db348a0b71c9b0a, < 3982714e15512b83115897806dacc94899683420; >= 40909f664d279765af430acc5db348a0b71c9b0a, < da7805f0211af19968584e621074f253ac07dba7; >= 40909f664d279765af430acc5db348a0b71c9b0a, < 1d4b5902773475fc97151379b7e5f09cad0fa57b; >= 40909f664d279765af430acc5db348a0b71c9b0a, < 229b42d7450c1cf96f45ec39ebb69211b06bc036
LinuxLinux5.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-93264?
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.
How severe is CVE-2026-93264?
Severity scoring for CVE-2026-93264 is pending analysis.
How do I fix CVE-2026-93264?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-93264?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST