CVE-2021-47265: RDMA: Verify port when creating flow rule
In the Linux kernel, the following vulnerability has been resolved:
RDMA: Verify port when creating flow rule
Validate port value provided by the user and with that remove no longer
needed validation by the driver. The missing check in the mlx5_ib driver
could cause to the below oops.
Call trace:
_create_flow_rule+0x2d4/0xf28 [mlx5_ib]
mlx5_ib_create_flow+0x2d0/0x5b0 [mlx5_ib]
ib_uverbs_ex_create_flow+0x4cc/0x624 [ib_uverbs]
ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0xd4/0x150 [ib_uverbs]
ib_uverbs_cmd_verbs.isra.7+0xb28/0xc50 [ib_uverbs]
ib_uverbs_ioctl+0x158/0x1d0 [ib_uverbs]
do_vfs_ioctl+0xd0/0xaf0
ksys_ioctl+0x84/0xb4
__arm64_sys_ioctl+0x28/0xc4
el0_svc_common.constprop.3+0xa4/0x254
el0_svc_handler+0x84/0xa0
el0_svc+0x10/0x26c
Code: b9401260 f9615681 51000400 8b001c20 (f9403c1a)
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects RDMA flow-rule creation. A user-supplied port value was not properly validated, which could trigger a kernel oops in the mlx5_ib RDMA driver. The available sources do not provide CVSS scoring, confirmed exploitation, or detailed business impact beyond the kernel crash evidence.
Executive priority
Treat this as a targeted infrastructure hygiene item, not an internet-wide emergency based on current evidence. Prioritize patch verification on RDMA-enabled Linux servers, especially high-availability compute, storage, or networking systems.
Technical view
CVE-2021-47265 is a Linux kernel RDMA/uverbs validation flaw. The fix validates the user-provided port before creating a flow rule, preventing mlx5_ib from reaching an invalid state that can produce the documented oops call trace during ib_uverbs flow creation.
Likely exposure
Exposure is most likely on Linux systems using RDMA/uverbs with mlx5_ib-capable hardware and affected kernel builds. Exact exposure depends on distro backports and whether RDMA interfaces are present and accessible.
Exploitation context
The source bundle shows no CISA KEV listing and no cited evidence of active exploitation. The described impact is a kernel oops triggered through RDMA flow-rule creation, but sources do not provide exploit prerequisites or real-world attack reports.
Researcher notes
The public record is sparse: no CVSS, CWE, exploit status, or detailed affected distro mapping is provided. Analysis should focus on kernel provenance, RDMA device exposure, and whether vendor kernels include the stable commits.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes in supported kernel packages.
Prioritize RDMA-enabled servers and systems using mlx5_ib hardware.
Follow vendor guidance if kernel updates are not immediately available.
Validation and detection
Inventory Linux kernel versions on RDMA-capable systems.
Confirm whether mlx5_ib and ib_uverbs are present or loaded.
Verify installed kernels include the referenced stable commits or distro backports.
Review kernel logs for mlx5_ib or ib_uverbs oops events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47265 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.