CVE-2025-38022

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/core: Fix "KASAN: slab-use-after-free Read in ib_register_device" problem<br /> <br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:94 [inline]<br /> dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120<br /> print_address_description mm/kasan/report.c:408 [inline]<br /> print_report+0xc3/0x670 mm/kasan/report.c:521<br /> kasan_report+0xe0/0x110 mm/kasan/report.c:634<br /> strlen+0x93/0xa0 lib/string.c:420<br /> __fortify_strlen include/linux/fortify-string.h:268 [inline]<br /> get_kobj_path_length lib/kobject.c:118 [inline]<br /> kobject_get_path+0x3f/0x2a0 lib/kobject.c:158<br /> kobject_uevent_env+0x289/0x1870 lib/kobject_uevent.c:545<br /> ib_register_device drivers/infiniband/core/device.c:1472 [inline]<br /> ib_register_device+0x8cf/0xe00 drivers/infiniband/core/device.c:1393<br /> rxe_register_device+0x275/0x320 drivers/infiniband/sw/rxe/rxe_verbs.c:1552<br /> rxe_net_add+0x8e/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:550<br /> rxe_newlink+0x70/0x190 drivers/infiniband/sw/rxe/rxe.c:225<br /> nldev_newlink+0x3a3/0x680 drivers/infiniband/core/nldev.c:1796<br /> rdma_nl_rcv_msg+0x387/0x6e0 drivers/infiniband/core/netlink.c:195<br /> rdma_nl_rcv_skb.constprop.0.isra.0+0x2e5/0x450<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline]<br /> netlink_unicast+0x53a/0x7f0 net/netlink/af_netlink.c:1339<br /> netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1883<br /> sock_sendmsg_nosec net/socket.c:712 [inline]<br /> __sock_sendmsg net/socket.c:727 [inline]<br /> ____sys_sendmsg+0xa95/0xc70 net/socket.c:2566<br /> ___sys_sendmsg+0x134/0x1d0 net/socket.c:2620<br /> __sys_sendmsg+0x16d/0x220 net/socket.c:2652<br /> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]<br /> do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> <br /> This problem is similar to the problem that the<br /> commit 1d6a9e7449e2 ("RDMA/core: Fix use-after-free when rename device name")<br /> fixes.<br /> <br /> The root cause is: the function ib_device_rename() renames the name with<br /> lock. But in the function kobject_uevent(), this name is accessed without<br /> lock protection at the same time.<br /> <br /> The solution is to add the lock protection when this name is accessed in<br /> the function kobject_uevent().