{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64485",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64485"
  ],
  "published": "2026-07-25T08:51:45Z",
  "summary": "ALSA: compress: Fix task creation error unwind",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: compress: Fix task creation error unwind\n\nsnd_compr_task_new() allocates the driver task before validating the\nreturned DMA buffers and reserving file descriptors. When either of\nthose later steps fails, the core frees its task wrapper and DMA-buffer\nreferences without calling the driver's task_free() callback. Any\ndriver resources allocated by task_create() are therefore leaked.\n\nThe dual-fd allocation path also jumps to cleanup without storing the\nnegative get_unused_fd_flags() result in retval. Since retval still\ncontains the successful task_create() return value, TASK_CREATE can\nincorrectly report success although the task was discarded.\n\nPreserve the fd allocation errors and call task_free() when failure\noccurs after a successful task_create() callback.",
  "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:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1",
        "1:6.18.34-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v6",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v7",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v6",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v7",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-2712",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v6",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v7",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.34-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          },
          "1:6.18.34-1+rpt1": {
            "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af",
            "upstream_version": "6.18.34",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64485"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b27a75d42044d9d4709095617730b91b1c4af423"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/426a9947a38d272d0e19c031658da68e31128667"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4a60127debb9e370d6c0e22a307326b624a141f3"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:24:08Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path requires opening the local ALSA compress accelerator device and issuing SET_PARAMS and TASK_CREATE ioctls; no network or physical-input path reaches it.\nAC:L - The attacker can deterministically exhaust its own file-descriptor table so descriptor allocation fails after task_create succeeds. No race or condition outside the attacker\u2019s control is required.\nPR:L - There are no capable(), ns_capable(), or authentication checks in this path, so an unprivileged user with ordinary access to the ASRC device node can trigger it.\nUI:N - The attacker alone can configure the stream, exhaust descriptors, issue TASK_CREATE, and close the stream. No separate victim action is required.\nS:U - The vulnerable ALSA driver and the affected kernel resources share the same security authority; kernel compromise is a conventional local privilege escalation.\nC:H - Skipping task_free leaves asrc->pair[] referencing a driver object that stream close subsequently frees, producing an attacker-reclaimable UAF in interrupt and power-management paths. Reclaimed DMA-channel pointers can influence kernel control flow and expose arbitrary kernel data.\nI:H - The stale pair is used for writes through completion handling and for an indirect device_terminate_all call through its DMA-channel pointer. Heap reclamation can therefore provide memory-corruption and control-flow-hijacking primitives.\nA:H - The leak exhausts the finite ASRC contexts and exclusive DMA channels, persistently disabling the device. Dereferencing the stale pair during interrupt or suspend/resume handling can also cause a kernel oops, panic, or hang."
    }
  }
}
