{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-43093",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-43093"
  ],
  "published": "2026-05-06T07:41:37Z",
  "summary": "xsk: tighten UMEM headroom validation to account for tailroom and min frame",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: tighten UMEM headroom validation to account for tailroom and min frame\n\nThe current headroom validation in xdp_umem_reg() could leave us with\ninsufficient space dedicated to even receive minimum-sized ethernet\nframe. Furthermore if multi-buffer would come to play then\nskb_shared_info stored at the end of XSK frame would be corrupted.\n\nHW typically works with 128-aligned sizes so let us provide this value\nas bare minimum.\n\nMulti-buffer setting is known later in the configuration process so\nbesides accounting for 128 bytes, let us also take care of tailroom space\nupfront.",
  "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.175",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43093"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5f123bc278bf4e3283d8606321bebbfd299f4384"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1a6051cd7e3e4c54ff3854a43b638b9292af5e67"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8769708add9eadeea8041a9761771bb715a87104"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a03975beb9f6af0d8ac051e30b2abeabe618414f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0ec4d3f6e6934deb843b561ae048cd17218e5ad1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6523bc1b40e69301f24c14338b762af4739d6d39"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a315e022a72d95ef5f1d4e58e903cb492b0ad931"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable UMEM headroom value is supplied through local AF_XDP socket setup via socket(), setsockopt(SOL_XDP, XDP_UMEM_REG), and bind(); network packets may later exercise the bad layout, but they do not create it.\nAC:L - The attacker controls the UMEM chunk size/headroom and AF_XDP setup parameters, and no race or rare timing condition is required.\nPR:L - AF_XDP socket creation requires CAP_NET_RAW in the network namespace and related XDP/BPF setup uses namespace-capable networking privileges, which are reachable by a low-privileged local user through user namespaces in reasonable configurations.\nUI:N - No victim action is needed once the attacker can run the local setup and drive traffic through the socket.\nS:U - The impact remains within the kernel/networking security authority and does not cross a VM, IOMMU, or similar scope boundary.\nC:H - The invalid UMEM geometry can corrupt skb_shared_info/fragment metadata consumed by kernel XDP/AF_XDP paths; under the required overestimation rule, this kernel metadata corruption is treated as capable of enabling high-impact information disclosure.\nI:H - The bug permits attacker-controlled layout overlap with kernel-used XDP fragment metadata, creating a plausible memory-corruption primitive rather than a mere validation failure.\nA:H - Malformed AF_XDP receive geometry can leave insufficient space even for minimum frames and corrupt multi-buffer metadata, making kernel/network path crashes or severe disruption plausible."
    }
  }
}