CVE-2026-93264

RDMA/efa: Fix PBL chunk length computation

N/A
Published: September 24, 2026 at 03:52 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

40909f664d279765af430acc5db348a0b71c9b0a5.2
Vendor states this is fixed in 1d4b5902773475fc97151379b7e5f09cad0fa57b (fixed)
Vendor states this is fixed in 229b42d7450c1cf96f45ec39ebb69211b06bc036 (fixed)
Vendor states this is fixed in 3982714e15512b83115897806dacc94899683420 (fixed)
Vendor states this is fixed in 489b28f2377afa70c18c45b06a6387f3d39bb123 (fixed)
Vendor states this is fixed in 665cd418b8561a099c3854443f8ad8ae751b72a0 (fixed)
Vendor states this is fixed in 932e5684906a090644a9061fae2d254041c3b8f2 (fixed)
Vendor states this is fixed in aadf3f9b5edb7f0a77e9172b237d2e07c754829c (fixed)
Vendor states this is fixed in da7805f0211af19968584e621074f253ac07dba7 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card