{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-80548",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-80548"
  ],
  "published": "2026-08-26T14:37:59Z",
  "summary": "s390/vfio_ccw: Selectively expand io_mutex",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/vfio_ccw: Selectively expand io_mutex\n\nThe io_mutex was defined to serialize the io_regions, but then has\nalso sort of been associated with the I/O themselves because of\nthe close relationship they share.\n\nWith the handful of races that are possible, the choices are either to:\n A) expand the scope of io_mutex to close these remaining windows, or\n B) reduce the scope of io_mutex to just io_region, and introduce a new\n    lock mechanism for the remaining I/O resources\n\nThis patch implements A, since B brings with it a lot more interactions\nthat would need to be tracked and kept in a correct hierarchy. It also\ntakes advantage of the workqueue element for cp_free() that now gets\ncalled out of fsm_notoper(), which could be invoked out of an interrupt\ncontext and thus cannot acquire a mutex itself.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.185",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80548"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/dab6a6627b0b0cce23653e99c7b0bf8c6cfd82e0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/56d7488533ceac4e986e96e15c9e487a2245bc01"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f72a51810d49411bd8cad0c2df8592320a2fe5cc"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2ba9efdf9ebedc4e54df4b56aa3b43a65f7967cd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b6aecea4b2b246f9fbd98a5712daa1193a60818e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2a5ac0c0f1f7da33929211a2e41911bf72ee35d8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/34f4feff3e90bd09308fad0974e97113b23b812a"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-27T12:40:42Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The bug is reached only through local VFIO mediated-device syscalls (read/write/ioctl on vfio-ccw device fds) and deferred work from hardware I/O interrupts and channel-path events; vfio-ccw has no network, Bluetooth, or physical-bus entry point.\nAC:L - The VFIO client controls both sides of each race window: it can submit channel I/O, close or reset the device, and trigger DMA unmap while io_work, notoper_work, or fsm_close concurrently run cp_free, cp_update_scsw, or cp_iova_pinned without full io_mutex protection, and retry to win reliably.\nPR:L - Exploitation requires an opened vfio-ccw mdev device fd (typical QEMU/libvirt VM operator or delegated /dev/vfio holder on IBM Z passthrough hosts), not init-namespace root; mdev creation is admin setup, but triggering the races needs only that delegated VFIO client access.\nUI:N - No separate victim action is required; once vfio-ccw passthrough is configured, the attacker issues concurrent channel I/O, region access, device close/reset, or DMA unmap without needing another user to mount media or interact.\nS:C - On IBM Z/LinuxONE, vfio-ccw passes DASD/CCW subchannels into KVM guests; guest-driven channel I/O and path events trigger host interrupt/workqueue activity concurrent with VFIO client teardown, corrupting hypervisor kernel memory outside the VM security boundary.\nC:H - cp_free racing with cp_update_scsw, cp_iova_pinned, and io_region access without io_mutex causes use-after-free on ccwchain_list and page_array structures; per kernel UAF guidance this enables attacker-influenced heap reuse and arbitrary kernel read primitives.\nI:H - Concurrent cp_free during cp_init, page_array_unpin_free, memcpy into io_region, and mutex operations on freed channel_program memory provides heap-sprayable arbitrary write and control-flow hijack potential beyond a simple crash.\nA:H - Use-after-free and double-free of channel program structures during concurrent I/O completion, not-operational cleanup, or device close can immediately oops or panic the host kernel from invalid list/mutex access, and successful exploitation can crash or hang the system."
    }
  }
}