{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-53110",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-53110"
  ],
  "published": "2024-12-02T13:53:05Z",
  "summary": "vp_vdpa: fix id_table array not null terminated error",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvp_vdpa: fix id_table array not null terminated error\n\nAllocate one extra virtio_device_id as null terminator, otherwise\nvdpa_mgmtdev_get_classes() may iterate multiple times and visit\nundefined memory.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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.119",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-53110"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/870d68fe17b5d9032049dcad98b5781a344a8657"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c4d64534d4b1c47d2f1ce427497f971ad4735aae"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0a886489d274596ad1a80789d3a773503210a615"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4e39ecadf1d2a08187139619f1f314b64ba7d947"
    }
  ],
  "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.3,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path is reached through a generic netlink socket (VDPA_CMD_MGMTDEV_GET on the vdpa genl family), which requires local system access. Per kernel scoring guidance, netlink-reachable code is Local.\nAC:L - The out-of-bounds read is fully deterministic \u2014 every MGMTDEV_GET doit or dump against a vp_vdpa management device walks past the single-entry allocation with no race, timing window, or attacker-uninfluenceable memory layout required.\nPR:L - VDPA_CMD_MGMTDEV_GET is registered without GENL_ADMIN_PERM (drivers/vdpa/vdpa.c:1544), unlike the sibling DEV_NEW/DEV_DEL/DEV_ATTR_SET ops, so any unprivileged local user can trigger the read and receive the reply; the dump variant needs no attributes at all.\nUI:N - The attacker triggers the bug entirely on their own by sending a netlink message; no victim action or cooperation is involved.\nS:U - The out-of-bounds read stays within the kernel's own heap and the impact is confined to the kernel security authority, with no crossing of a VM, IOMMU, or sandbox boundary.\nC:H - The read is unbounded \u2014 it walks adjacent slab memory until it chances upon a zero word \u2014 and the derived value is returned to the unprivileged caller in VDPA_ATTR_DEV_MGMTDEV_SUPPORTED_CLASSES, disclosing adjacent heap contents rather than a strictly bounded few bytes.\nI:L - Garbage device IDs harvested out of bounds are folded into the classes bitmask and ncls counter that gate the class-consistency validation in vdpa_nl_cmd_dev_add_set_doit(), so out-of-bounds heap data can alter kernel device-creation decisions in a limited way.\nA:H - The unterminated walk can run far past the object into a non-present region and oops the kernel, and on KASAN-instrumented builds the slab-out-of-bounds report panics under panic_on_warn; the read is repeatable at will by an unprivileged user."
    }
  }
}