{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2025-38022",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2025-38022"
  ],
  "published": "2025-06-18T09:29:20Z",
  "summary": "RDMA/core: Fix \"KASAN: slab-use-after-free Read in ib_register_device\" problem",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix \"KASAN: slab-use-after-free Read in ib_register_device\" problem\n\nCall Trace:\n\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:408 [inline]\n print_report+0xc3/0x670 mm/kasan/report.c:521\n kasan_report+0xe0/0x110 mm/kasan/report.c:634\n strlen+0x93/0xa0 lib/string.c:420\n __fortify_strlen include/linux/fortify-string.h:268 [inline]\n get_kobj_path_length lib/kobject.c:118 [inline]\n kobject_get_path+0x3f/0x2a0 lib/kobject.c:158\n kobject_uevent_env+0x289/0x1870 lib/kobject_uevent.c:545\n ib_register_device drivers/infiniband/core/device.c:1472 [inline]\n ib_register_device+0x8cf/0xe00 drivers/infiniband/core/device.c:1393\n rxe_register_device+0x275/0x320 drivers/infiniband/sw/rxe/rxe_verbs.c:1552\n rxe_net_add+0x8e/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:550\n rxe_newlink+0x70/0x190 drivers/infiniband/sw/rxe/rxe.c:225\n nldev_newlink+0x3a3/0x680 drivers/infiniband/core/nldev.c:1796\n rdma_nl_rcv_msg+0x387/0x6e0 drivers/infiniband/core/netlink.c:195\n rdma_nl_rcv_skb.constprop.0.isra.0+0x2e5/0x450\n netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline]\n netlink_unicast+0x53a/0x7f0 net/netlink/af_netlink.c:1339\n netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1883\n sock_sendmsg_nosec net/socket.c:712 [inline]\n __sock_sendmsg net/socket.c:727 [inline]\n ____sys_sendmsg+0xa95/0xc70 net/socket.c:2566\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2620\n __sys_sendmsg+0x16d/0x220 net/socket.c:2652\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThis problem is similar to the problem that the\ncommit 1d6a9e7449e2 (\"RDMA/core: Fix use-after-free when rename device name\")\nfixes.\n\nThe root cause is: the function ib_device_rename() renames the name with\nlock. But in the function kobject_uevent(), this name is accessed without\nlock protection at the same time.\n\nThe solution is to add the lock protection when this name is accessed in\nthe function kobject_uevent().",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.160",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2025-38022"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ba467b6870ea2a73590478d9612d6ea1dcdd68b7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5629064f92f0de6d6b3572055cd35361c3ad953c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/312dae3499106ec8cb7442ada12be080aa9fbc3b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/17d3103325e891e10994e7aa28d12bea04dc2c60"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/10c7f1c647da3b77ef8827d974a97b6530b64df0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/03df57ad4b0ff9c5a93ff981aba0b42578ad1571"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d0706bfd3ee40923c001c6827b786a309e2a8713"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T12:19:11Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - Both sides of the race are reached via `sendmsg()` on a local NETLINK_RDMA socket (`rdma_nl_rcv_msg` \u2192 `nldev_newlink` / `nldev_set_doit`), which requires local system access. No remote peer data reaches the vulnerable code.\nAC:L - The attacker controls both sides of the race, looping RDMA_NLDEV_CMD_NEWLINK in one thread and RDMA_NLDEV_CMD_SET (rename) in another; `enable_device_and_get()` marks the device DEVICE_REGISTERED and drops to refcount 2 before the unprotected `kobject_uevent()`, leaving a reliably hittable window that syzkaller reproduced.\nPR:L - The gate is `netlink_capable(skb, CAP_NET_ADMIN)`, which checks init_user_ns and so is not obtainable via `unshare -Urn`, but CAP_NET_ADMIN in the initial user namespace is routinely delegated to non-root, container-confined workloads (Docker/K8s do not enable user namespaces by default, and RDMA/SR-IOV network plugins commonly run with `--cap-add=NET_ADMIN`). Scored as a low-privileged principal rather than real host root.\nUI:N - The attacker triggers both the device registration and the concurrent rename entirely on its own via netlink; no victim action is involved.\nS:U - The use-after-free is in kernel slab memory and its impact stays within the kernel's security authority; no hypervisor, IOMMU, or sandbox boundary is crossed.\nC:H - The freed `kobj->name` slab object is `strlen`'d and `memcpy`'d into the `DEVPATH=` uevent variable that is broadcast to userspace listeners and the uevent helper, so reallocated kernel heap contents are disclosed outside the kernel, and the unterminated `strlen` reads out of bounds past the freed chunk.\nI:H - This is a slab use-after-free where the attacker can spray the freed kmalloc chunk and control the data the kernel then consumes; per UAF-class scoring the reallocation primitive is treated as exploitable for kernel state corruption, and the resulting bogus DEVPATH also drives userspace device management onto the wrong sysfs path.\nA:H - KASAN reports a slab-use-after-free read that can fault and oops when the backing page is freed or under KFENCE/page poisoning, and `kobject_get_path()`'s `retry` loop can spin under a sustained rename storm, both causing denial of service."
    }
  }
}