CVE-2026-93264: RDMA/efa: Fix PBL chunk length computation

Published Sep 24, 2026
·
Updated

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 (EFAPTRSPERCHUNK) 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 EFAPTRSPERCHUNK, 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 EFAPTRSPERCHUNK, 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

1 affected component
Linux Linux kernel

Event History

Sep 24, 2026
CVE Published
via MITRE·03:52 PM
Data Sourced
via MITRE·03:52 PM
Description
Data Sourced
via NVD·04:17 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel EFA RDMA driver and registering memory regions that require an indirect PBL are affected when the PBL page count is an exact multiple of 510. The issue occurs during memory registration rather than for all EFA driver activity.

2

What is the practical impact when the condition is triggered?

The final PBL chunk can be treated as empty because its length is computed as zero. The device can then reject the memory registration, and the faulty handling can also reach beyond the chunks array.

3

How can I determine whether a failure may be related to this issue?

Investigate failed EFA memory-registration operations where the indirect PBL contains a page count divisible by 510. This condition causes the final fully populated chunk to be supplied with a zero length.

4

Is there a workaround if an updated kernel cannot be deployed immediately?

Avoid memory-registration layouts that produce an indirect PBL page count exactly divisible by 510, where feasible. The corrected kernel logic preserves the full length for such final chunks and prevents the out-of-bounds array access.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203