Skip to content
Heist/ feed
Back to feed
UnratedFix available

ALSA: FCP: Use a private URB for the notification endpoint

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: Use a private URB for the notification endpoint fcp_init_notify() used mixer->urb, which snd_usb_mixer_status_create() allocates for the optional UAC2 status interrupt endpoint and mixer.c kills, resubmits and frees. On a device with that endpoint, fcp_init_notify()'s "already set up" early return fires on the status URB and returns success without doing anything. No FCP notification URB is submitted, and cmd_done is left zeroed because it is initialised past that early return and nowhere else. fcp_init() then issues init1_opcode and wait_for_completion_timeout() would crash adding to the zeroed wait.head. fcp_cleanup_urb() would also kill and free mixer.c's status URB. Use a separate URB in fcp_data, and initialise cmd_done in fcp_init_private() where fcp_data is allocated. fcp_init_notify() is reached again after suspend via fcp_reinit(), and the URB kill path in fcp_notify() completes cmd_done, leaving a stale count that would satisfy the next command's wait before the device ACKs. Use reinit_completion() to clear it.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.47, 7.1.11, 7.2.1
CVEs
CVE-2026-80816
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 03:22 UTC · Revision 1

Source evidence

ALSA: FCP: Use a private URB for the notification endpoint

core-osv · Original source

Published 4 Sept 2026, 15:13 UTC

In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: Use a private URB for the notification endpoint fcp_init_notify() used mixer->urb, which snd_usb_mixer_status_create() allocates for the optional UAC2 status interrupt endpoint and mixer.c kills, resubmits and frees. On a device with that endpoint, fcp_init_notify()'s "already set up" early return fires on the status URB and returns success without doing anything. No FCP notification URB is submitted, and cmd_done is left zeroed because it is initialised past that early return and nowhere else. fcp_init() then issues init1_opcode and wait_for_completion_timeout() would crash adding to the zeroed wait.head. fcp_cleanup_urb() would also kill and free mixer.c's status URB. Use a separate URB in fcp_data, and initialise cmd_done in fcp_init_private() where fcp_data is allocated. fcp_init_notify() is reached again after suspend via fcp_reinit(), and the URB kill path in fcp_notify() completes cmd_done, leaving a stale count that would satisfy the next command's wait before the device ACKs. Use reinit_completion() to clear it.

osv:CVE-2026-80816

Kernel

Fixed versions: 6.18.47, 7.1.11, 7.2.1

Complete source record
{
  "id": "2e8c9475da51a29cfc88b8deeed305f66c0d72b0f2d723cdabe5c0c5e5e8a294",
  "url": "https://osv.dev/vulnerability/CVE-2026-80816",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ALSA: FCP: Use a private URB for the notification endpoint",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: Use a private URB for the notification endpoint fcp_init_notify() used mixer->urb, which snd_usb_mixer_status_create() allocates for the optional UAC2 status interrupt endpoint and mixer.c kills, resubmits and frees. On a device with that endpoint, fcp_init_notify()'s \"already set up\" early return fires on the status URB and returns success without doing anything. No FCP notification URB is submitted, and cmd_done is left zeroed because it is initialised past that early return and nowhere else. fcp_init() then issues init1_opcode and wait_for_completion_timeout() would crash adding to the zeroed wait.head. fcp_cleanup_urb() would also kill and free mixer.c's status URB. Use a separate URB in fcp_data, and initialise cmd_done in fcp_init_private() where fcp_data is allocated. fcp_init_notify() is reached again after suspend via fcp_reinit(), and the URB kill path in fcp_notify() completes cmd_done, leaving a stale count that would satisfy the next command's wait before the device ACKs. Use reinit_completion() to clear it.",
    "evidence": "osv:CVE-2026-80816",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.47",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.1.11",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.2.1",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-80816",
      "aliases": [
        "CVE-2026-80816"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "46757a3e7d50dac923888e7fbe68377736f13c70"
                },
                {
                  "fixed": "65aceb45ca91ddb7f7ed178821f481b34da35543"
                },
                {
                  "fixed": "5da21a434171e8ecf1d992c6f1d84c0c706fd395"
                },
                {
                  "fixed": "6db3c1d7e2872c9904e05ca8e0515920776a3c9c"
                },
                {
                  "fixed": "918b8d231c571c50a00efe92ffc8404a537a0490"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80816.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.14.0"
                },
                {
                  "fixed": "6.18.47"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.1.11"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "7.2.0"
                },
                {
                  "fixed": "7.2.1"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-80816.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:25.484227788Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/5da21a434171e8ecf1d992c6f1d84c0c706fd395",
        "https://git.kernel.org/stable/c/65aceb45ca91ddb7f7ed178821f481b34da35543",
        "https://git.kernel.org/stable/c/6db3c1d7e2872c9904e05ca8e0515920776a3c9c",
        "https://git.kernel.org/stable/c/918b8d231c571c50a00efe92ffc8404a537a0490",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80816.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-80816",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/80xxx/CVE-2026-80816.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-80816",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 492153,
  "published_at": "2026-09-04T15:13:37.31+00:00"
}