RDMA/rxe: Flush delayed SKBs while releasing RXE resources
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.446.16.46.17In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Flush delayed SKBs while releasing RXE resources
When skb packets are sent out, these skb packets still depends on the rxe resources, for example, QP, sk, when these packets are destroyed.
If these rxe resources are released when the skb packets are destroyed, the call traces will appear.
To avoid skb packets hang too long time in some network devices, a timestamp is added when these skb packets are created. If these skb packets hang too long time in network devices, these network devices can free these skb packets to release rxe resources.
From the CVE record · Linux
The Linux kernel's RDMA/rxe component can produce call traces when RXE resources are released while delayed skb packets still depend on them. This occurs when packets remain in network devices until their associated resources are released; the input does not describe an attacker action, authentication requirement, or user interaction.
Engineers running Linux kernels with RDMA/rxe should check their installations; affected versions were not provided.