{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.11-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  media: verisilicon: Fix kernel panic due to __initconst misuse  Fix a kernel panic when probing the driver as a module:    Unable to handle kernel paging request at virtual address   ffffd9c18eb05000   of_find_matching_node_and_match+0x5c/0x1a0   hantro_probe+0x2f4/0x7d0 [hantro_vpu]  The imx8mq_vpu_shared_resources array is referenced by variant structures through their shared_devices field. When built as a module, __initconst causes this data to be freed after module init, but it's later accessed during probe, causing a page fault.  The imx8mq_vpu_shared_resources is referenced from non-init code, so keeping __initconst or __initconst_or_module here is wrong.  Drop the __initconst annotation and let it live in the normal .rodata section.  A bug of __initconst called from regular non-init probe code leading to bugs during probe deferrals or during unbind-bind cycles.",
  "id": "DEBIAN-CVE-2026-31573",
  "modified": "2026-04-28T19:49:39.617999650Z",
  "published": "2026-04-24T15:16:31.857Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31573"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31573"
  ]
}