{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.6-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  iommu/vt-d: Fix race condition during PASID entry replacement  The Intel VT-d PASID table entry is 512 bits (64 bytes). When replacing an active PASID entry (e.g., during domain replacement), the current implementation calculates a new entry on the stack and copies it to the table using a single structure assignment.          struct pasid_entry *pte, new_pte;          pte = intel_pasid_get_entry(dev, pasid);         pasid_pte_config_first_level(iommu, \u0026new_pte, ...);         *pte = new_pte;  Because the hardware may fetch the 512-bit PASID entry in multiple 128-bit chunks, updating the entire entry while it is active (Present bit set) risks a \"torn\" read. In this scenario, the IOMMU hardware could observe an inconsistent state — partially new data and partially old data — leading to unpredictable behavior or spurious faults.  Fix this by removing the unsafe \"replace\" helpers and following the \"clear-then-update\" flow, which ensures the Present bit is cleared and the required invalidation handshake is completed before the new configuration is applied.",
  "id": "DEBIAN-CVE-2026-45945",
  "modified": "2026-09-14T16:47:43.137973824Z",
  "published": "2026-05-27T14:17:10.790Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-45945"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-45945"
  ]
}