{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.176-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.94-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.12-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  parport: Fix race between port and client registration  The parport subsystem registers port devices before they are fully initialised, resulting in a race condition where client drivers such as lp can attach to ports that are not completely initialised or even being torn down.  When the port and client drivers are built as modules and loaded around the same time during boot, this occasionally results in a crash.  I was able to make this happen reliably in a VM with a PC-style parallel port by patching parport_pc to fail probing:  \u003e --- a/drivers/parport/parport_pc.c \u003e +++ b/drivers/parport/parport_pc.c \u003e @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base, \u003e  \tif (!p) \u003e  \t\tgoto out3; \u003e \u003e -\tbase_res = request_region(base, 3, p-\u003ename); \u003e +\tbase_res = NULL; \u003e  \tif (!base_res) \u003e  \t\tgoto out4; \u003e  and then running:      while true; do         modprobe lp \u0026 modprobe parport_pc \twait \trmmod lp parport_pc     done  for a few seconds.  In the long term I think port registration should be changed to put the call to device_add() inside parport_announce_port(), but since the latter currently cannot fail this will require changing all port drivers.  For now, add a flag to indicate whether a port has been \"announced\" and only try to attach client drivers to ports when the flag is set.",
  "id": "DEBIAN-CVE-2026-63942",
  "modified": "2026-09-14T16:47:33.469417251Z",
  "published": "2026-07-19T16:17:12.747Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-63942"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-63942"
  ]
}