CVE-2024-57795: RDMA/rxe: Remove the direct link to net_device
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Remove the direct link to net_device
The similar patch in siw is in the link:
https://git.kernel.org/rdma/rdma/c/16b87037b48889
This problem also occurred in RXE. The following analyze this problem.
In the following Call Traces:
"
BUG: KASAN: slab-use-after-free in dev_get_flags+0x188/0x1d0 net/core/dev.c:8782
Read of size 4 at addr ffff8880554640b0 by task kworker/1:4/5295
CPU: 1 UID: 0 PID: 5295 Comm: kworker/1:4 Not tainted
6.12.0-rc3-syzkaller-00399-g9197b73fd7bb #0
Hardware name: Google Compute Engine/Google Compute Engine,
BIOS Google 09/13/2024
Workqueue: infiniband ib_cache_event_task
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:377 [inline]
print_report+0x169/0x550 mm/kasan/report.c:488
kasan_report+0x143/0x180 mm/kasan/report.c:601
dev_get_flags+0x188/0x1d0 net/core/dev.c:8782
rxe_query_port+0x12d/0x260 drivers/infiniband/sw/rxe/rxe_verbs.c:60
__ib_query_port drivers/infiniband/core/device.c:2111 [inline]
ib_query_port+0x168/0x7d0 drivers/infiniband/core/device.c:2143
ib_cache_update+0x1a9/0xb80 drivers/infiniband/core/cache.c:1494
ib_cache_event_task+0xf3/0x1e0 drivers/infiniband/core/cache.c:1568
process_one_work kernel/workqueue.c:3229 [inline]
process_scheduled_works+0xa65/0x1850 kernel/workqueue.c:3310
worker_thread+0x870/0xd30 kernel/workqueue.c:3391
kthread+0x2f2/0x390 kernel/kthread.c:389
ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
"
1). In the link [1],
"
infiniband syz2: set down
"
This means that on 839.350575, the event ib_cache_event_task was sent andi
queued in ib_wq.
2). In the link [1],
"
team0 (unregistering): Port device team_slave_0 removed
"
It indicates that before 843.251853, the net device should be freed.
3). In the link [1],
"
BUG: KASAN: slab-use-after-free in dev_get_flags+0x188/0x1d0
"
This means that on 850.559070, this slab-use-after-free problem occurred.
In all, on 839.350575, the event ib_cache_event_task was sent and queued
in ib_wq,
before 843.251853, the net device veth was freed.
on 850.559070, this event was executed, and the mentioned freed net device
was called. Thus, the above call trace occurred.
[1] https://syzkaller.appspot.com/x/log.txt?x=12e7025f980000
Security readout for executives and security teams
Plain-English summary
A Linux RDMA software driver can retain a reference to a network device after that device is removed. Delayed kernel work may then access freed memory, potentially crashing the system or corrupting kernel memory. The CVSS assessment is 7.8 and requires local, low-privileged access; remote exploitation is not established by the supplied evidence.
Executive priority
Treat this as a high-priority local kernel issue on systems using RXE, especially shared or multi-user hosts. Patch through normal emergency kernel processes after compatibility testing. Systems without RXE are lower priority, but confirm configuration rather than assuming non-exposure.
Technical view
CVE-2024-57795 is a CWE-416 use-after-free in the RXE RDMA driver. An RDMA cache event can remain queued while its directly referenced net_device is unregistered and freed. Later, rxe_query_port calls dev_get_flags through the stale reference. Stable-kernel commits remove the direct link to net_device.
Likely exposure
Exposure is limited to Linux systems using the RXE software RDMA functionality. The bundle lists 4.8, 6.6.120, 6.12.9, and 6.13 as affected, but does not clearly express complete version ranges. Distribution backports may alter exposure, so kernel package versions alone are insufficient.
Exploitation context
The supplied CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. Syzkaller triggered the flaw on a 6.12 release candidate. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a publicly weaponized exploit.
Researcher notes
The evidence demonstrates a lifecycle race: work is queued, the associated net_device is freed, and delayed RDMA cache processing dereferences it. The observed KASAN trace establishes memory-safety impact, but the bundle does not demonstrate reliable privilege escalation, confidentiality loss, or exploitation outside a test environment. Exact affected-version boundaries remain unclear.
Mitigation direction
Update to a vendor-supported kernel containing the applicable stable fix commit.
Confirm distribution backports with the Linux distributor or appliance vendor.
Prioritize systems where RXE software RDMA is enabled or operationally required.
If updating is delayed, seek vendor-supported mitigations; none are named in the supplied sources.
Validation and detection
Inventory Linux kernel releases and identify hosts using RXE software RDMA.
Map installed vendor kernel builds to the three referenced stable fix commits.
Review kernel logs for use-after-free reports involving rxe_query_port, dev_get_flags, or ib_cache_event_task.
After updating, verify the running kernel includes the vendor backport or applicable upstream fix.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.