{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-53103",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-53103"
  ],
  "published": "2024-12-02T07:29:40Z",
  "summary": "hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer\n\nWhen hvs is released, there is a possibility that vsk->trans may not\nbe initialized to NULL, which could lead to a dangling pointer.\nThis issue is resolved by initializing vsk->trans to NULL.",
  "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.117",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-53103"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/285266ef92f7b4bf7d26e1e95e215ce6a6badb4a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4fe1d42f2acc463b733bb42e3f8e67dbc2a0eb2d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/414476c4fb11be070c09ab8f3e75c9ee324a108a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7cf25987820350cb950856c71b409e5b6eed52bd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/98d8dde9232250a57ad5ef16479bf6a349e09b80"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e0fe3392371293175f25028020ded5267f4cd8e3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8621725afb38e111969c64280b71480afde2aace"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e629295bd60abf4da1db85b82819ca6a4f6c1e79"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable code is reached through the AF_VSOCK socket API (`socket()`/`connect()`) from a local process in the guest; there is no path that lets a remote or adjacent peer drive the transport reassignment. Per kernel scoring convention vsock bugs are Local.\nAC:L - The attacker fully controls the trigger sequence \u2014 `connect()` to VMADDR_CID_HOST to get the hv_sock transport, self-delivered signal (alarm/timer) to force the `SS_UNCONNECTED`/`TCP_CLOSING` state at af_vsock.c:1524, then `connect()` to VMADDR_CID_LOCAL to force `hvs_destruct()` \u2014 and can retry the sequence indefinitely with cheap, attacker-controlled heap grooming.\nPR:L - `vsock_create()` performs no capability check, so any unprivileged local user can create AF_VSOCK sockets and drive `vsock_connect()`; the required hv_sock and vsock_loopback modules are autoloaded by that unprivileged `socket()` call via MODULE_ALIAS_NETPROTO(PF_VSOCK).\nUI:N - The entire sequence is performed by the attacker's own process through ordinary syscalls; no action by any other user or administrator is needed.\nS:U - The dangling `struct hvsock` and the corrupted kernel heap are within the guest kernel's own security authority; hv_sock is the guest-side transport, so there is no crossing into the Hyper-V host or another VM.\nC:H - A dangling `vsk->trans` gives a use-after-free on a kmalloc'd `struct hvsock`; reclaiming that slot with attacker-chosen data and having `hvs_stream_dequeue()`/`hvs_update_recv_data()` read through the stale `recv_desc`/`recv_data_off`/`recv_data_len` fields yields controlled kernel memory disclosure into userspace.\nI:H - The same UAF is a write primitive \u2014 `hvs_open_connection()` does `hvs->chan = chan` and `hvs_update_recv_data()` writes `recv_data_len`/`recv_data_off` into the freed object, so heap spraying over the reclaimed slot allows corruption of an adjacent/overlapping kernel object and control-flow hijacking.\nA:H - Even without successful exploitation the stale pointer causes dereference of freed memory (or a NULL `vsk->transport` deref from `hvs_close_timeout` \u2192 `vsock_stream_has_data()`), producing a kernel oops/panic that an unprivileged user can trigger repeatedly."
    }
  }
}