{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-43283",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-43283"
  ],
  "published": "2026-05-06T11:29:17Z",
  "summary": "net: ethernet: ec_bhf: Fix dma_free_coherent() dma handle",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: ec_bhf: Fix dma_free_coherent() dma handle\n\ndma_free_coherent() in error path takes priv->rx_buf.alloc_len as\nthe dma handle. This would lead to improper unmapping of the buffer.\n\nChange the dma handle to priv->rx_buf.alloc_phys.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.165",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43283"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0f589ee54fd6d76d3f75e745f7f12c64cbd749e5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/accd0599bc8e73b962247c6c6c70ca7aa1f8e8d0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8320727be7ff704e07c87624efc2a4a75f54b3ce"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1e300c33ef3cc544c2b9c693778fe9490cfe9184"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1b1371cd4032ae859838ebc74215f569987bb197"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1b1d3c5d58a80a19d017a409aa2308162bab5bbf"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7e54ff938bebb173822b4c38b33fc164c1cabf92"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ffe68c3766997d82e9ccaf1cdbd47eba269c4aa2"
    }
  ],
  "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": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path is reached by local netdevice administration via RTM_SETLINK or SIOCSIFFLAGS setting IFF_UP, which calls ec_bhf_open(). Received EtherCAT packets do not directly reach the bad dma_free_coherent() error path.\nAC:L - An attacker who can administer the netdev can repeatedly attempt link-up under memory pressure until TX coherent allocation fails after RX allocation succeeds. No race or external timing condition is required.\nPR:L - The path requires CAP_NET_ADMIN in the owning network namespace, and this physical netdev is movable because the driver does not mark it netns_immutable. In a reasonable delegated/container netns deployment, namespace admin privileges are sufficient.\nUI:N - No separate victim interaction is needed once the attacker has access to the local netlink/ioctl control path. The attacker can trigger the open error path directly with link-up attempts.\nS:C - The wrong DMA handle can leave a stale DMA/IOMMU mapping or free the wrong physical pages, allowing device DMA beyond the intended lifetime of the RX buffer. This crosses the intended DMA isolation boundary.\nC:H - Stale DMA access or freeing the wrong in-use pages can expose reused kernel memory through memory corruption. As a DMA lifetime/memory corruption issue, high confidentiality impact is defensible.\nI:H - The bug can let the device write received data into freed or incorrectly freed kernel memory, creating a kernel memory corruption primitive. Such corruption is potentially usable for arbitrary kernel memory modification or code execution.\nA:H - Passing an invalid DMA handle to dma_free_coherent() can corrupt allocator/IOMMU state or free the wrong pages. At minimum this can cause kernel warnings, oopses, or panics."
    }
  }
}