{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-27073",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-27073"
  ],
  "published": "2024-05-01T13:06:43Z",
  "summary": "media: ttpci: fix two memleaks in budget_av_attach",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ttpci: fix two memleaks in budget_av_attach\n\nWhen saa7146_register_device and saa7146_vv_init fails, budget_av_attach\nshould free the resources it allocates, like the error-handling of\nttpci_budget_init does. Besides, there are two fixme comment refers to\nsuch deallocations.",
  "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.83",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-27073"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/af37aed04997e644f7e1b52b696b62dcae3cc016"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/910363473e4bf97da3c350e08d915546dd6cc30b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/24e51d6eb578b82ff292927f14b9f5ec05a46beb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/55ca0c7eae8499bb96f4e5d9b26af95e89c4e6a0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7393c681f9aa05ffe2385e8716989565eed2fe06"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1597cd1a88cfcdc4bf8b1b44cd458fed9a5a5d63"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/656b8cc123d7635dd399d9f02594f27aa797ac3c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d0b07f712bf61e1a3cf23c87c663791c42e50837"
    }
  ],
  "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 a PCI probe-time attach callback, and the resulting dangling state is exercised through local device files (/dev/dvb/adapterN/demux0, dvr0, dvbnet); there is no remote or adjacent-network path into budget_av_attach.\nAC:L - Once the failure branch has been taken, the attacker deterministically drives the use-after-free by opening the still-registered dvr0/demux0 node and starting a feed, with no race to win and unlimited retries.\nPR:L - Reaching the stale DVB character devices requires only an unprivileged local account with access to /dev/dvb, which is the norm for the video group on desktops and for the media/DVB application account on the set-top-box and embedded systems that carry these ttpci cards.\nUI:N - No victim action is needed; the leaked and dangling registrations are created automatically during driver probe and remain live until reboot.\nS:U - The freed saa7146_dev object, the leaked budget_av allocation and the orphaned DVB/i2c registrations all live inside the kernel's own security authority, crossing no VM, IOMMU or sandbox boundary.\nC:H - budget->dev is left pointing at kmem_cache memory freed by saa7146_init_one's error path, so subsequent demux/dvr operations read attacker-groomable freed slab contents (including the dev->mem MMIO pointer), a use-after-free that can be leveraged for kernel information disclosure.\nI:H - start_ts_capture() performs saa7146_write() through the freed device's dev->mem pointer, so an attacker who reclaims that slab controls the destination of kernel writel() operations, yielding a write primitive suitable for control-flow hijacking.\nA:H - Beyond the unbounded leak of the budget_av allocation, the DMA page table and the pinned module reference, any access to the orphaned demux/dvr/dvbnet nodes dereferences freed memory and performs MMIO through an iounmap'd mapping, reliably oopsing or panicking the kernel."
    }
  }
}