{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-43207",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-43207"
  ],
  "published": "2026-05-06T11:29:17Z",
  "summary": "media: mtk-mdp: Fix error handling in probe function",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: mtk-mdp: Fix error handling in probe function\n\nAdd mtk_mdp_unregister_m2m_device() on the error handling path to prevent\nresource leak.\n\nAdd check for the return value of vpu_get_plat_device() to prevent null\npointer dereference. And vpu_get_plat_device() increases the reference\ncount of the returned platform device. Add platform_device_put() to\nprevent reference leak.",
  "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.165",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-43207"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9d9c67976eda502edc6b3a148a1c5b6a18b69a98"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0bc43eaf021347f8d5aba87712c36b799695eec6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9d7962d5c81d6cf3f8dbdb5c71c57600bac5772b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/12cafc15d24611bfb43c82877b1bbb7454a85d5a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c8737d33d4e8ffae87e5d5edac17f8a705235cc2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b3fc99fe5b25613dd61c57bc70b8479adff4f60d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2e8f53a7382943411557e370f1a4f3946624a30e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8a8a3232abac5b972058a5f2cb3e33199d2a8648"
    }
  ],
  "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 code is in the MediaTek MDP platform-driver probe/error path and the leaked V4L2 mem2mem device is reachable through local `/dev/video*` access, not through network, adjacent radio, or physical hotplug input.\nAC:L - There is no race or probabilistic trigger; once the VPU lookup/registration error condition occurs, the old probe path deterministically dereferences NULL or leaves the registered video device without proper cleanup.\nPR:L - A low-privileged local user with access to the exposed V4L2 device can open/ioctl the leaked node after probe failure. Although an administrator can also induce the probe failure via driver binding/module state, the higher-severity reasonable scenario is local exploitation of an already leaked device node.\nUI:N - No victim action is needed after the vulnerable device state exists; the attacker directly triggers the local device operation.\nS:U - The impact remains within the kernel/device security authority and does not cross a VM, IOMMU, or separate trust-boundary scope.\nC:H - The missing `mtk_mdp_unregister_m2m_device()` can leave a V4L2 device pointing at probe-owned `mtk_mdp_dev` state that is released on probe failure, creating a use-after-free style primitive. Per kernel CVSS guidance, such memory corruption is scored as high confidentiality impact.\nI:H - The dangling V4L2 path can write through freed/reused kernel structures during open and later mem2mem operations, making control-flow or data corruption plausible. Per kernel CVSS guidance, UAF-style memory corruption is high integrity impact.\nA:H - The direct NULL dereference in `vpu_wdt_reg_handler(NULL, ...)` can crash the kernel, and the leaked dangling video device can also produce kernel oopses. Kernel crash/oops conditions are high availability impact."
    }
  }
}