{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-50189",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-50189"
  ],
  "published": "2024-11-08T05:39:01Z",
  "summary": "HID: amd_sfh: Switch to device-managed dmam_alloc_coherent()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: amd_sfh: Switch to device-managed dmam_alloc_coherent()\n\nUsing the device-managed version allows to simplify clean-up in probe()\nerror path.\n\nAdditionally, this device-managed ensures proper cleanup, which helps to\nresolve memory errors, page faults, btrfs going read-only, and btrfs\ndisk corruption.",
  "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.113",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-50189"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8c6ad37e5882073cab84901a31da9cb22f316276"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4cd9c5a0fcadc39a05c978a01e15e0d1edc4be93"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1c3b4c90479aa0375ec98fe1a802993ff96a5f47"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9dfee956f53eea96d93ef1e13ab4ce020f4c58b3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c56f9ecb7fb6a3a90079c19eb4c8daf3bbf514b3"
    }
  ],
  "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 in the AMD SFH PCIe HID driver, reachable only through local driver lifecycle events (boot-time probe/discovery failure, driver unbind/rebind, module unload) on affected AMD laptops. There is no network, adjacent-network, or removable-device path to the flaw.\nAC:L - The premature dma_free_coherent() happens deterministically on every teardown, and in the probe-failure path no stop command is ever sent so the firmware DMAs into the freed pages indefinitely; a local attacker can reliably shape which structures land on the recycled pages via memory pressure. Multiple independent reporters reproduced the corruption on stock systems.\nPR:L - The damaging state arises during automatic boot-time probe with no privileged action at all, and a basic local user can drive page reallocation into the stale-DMA target; no capability check gates the resulting memory corruption.\nUI:N - The probe error path executes from the driver's init workqueue during boot with no user present, and teardown-time frees need no victim action. Nothing must be opened, mounted, or clicked.\nS:U - The corrupted memory is ordinary kernel memory managed by the same security authority as the driver. dma_free_coherent() tears down any IOMMU mapping, so this is stale DMA on untranslated configurations rather than a DMA/IOMMU boundary bypass.\nC:H - Freed coherent pages return to the buddy allocator and can be handed to page cache, slab, or userspace, so the write-after-free corrupts arbitrary reallocated kernel objects and can be leveraged into disclosure of their contents. Sensor data is also deposited into whatever memory now owns those pages.\nI:H - The MP2 co-processor repeatedly writes 32 bytes into memory the kernel has reassigned, giving an uncontrolled kernel write primitive; reporters observed this propagate to persistent btrfs metadata corruption on disk.\nA:H - The stale DMA produced page faults, kernel memory errors, and btrfs filesystems forced read-only, i.e. system crashes and loss of filesystem availability."
    }
  }
}