{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "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:  ima: verify the previous kernel's IMA buffer lies in addressable RAM  Patch series \"Address page fault in ima_restore_measurement_list()\", v3.  When the second-stage kernel is booted via kexec with a limiting command line such as \"mem=\u003csize\u003e\" we observe a pafe fault that happens.      BUG: unable to handle page fault for address: ffff97793ff47000     RIP: ima_restore_measurement_list+0xdc/0x45a     #PF: error_code(0x0000)  not-present page  This happens on x86_64 only, as this is already fixed in aarch64 in commit: cbf9c4b9617b (\"of: check previous kernel's ima-kexec-buffer against memory bounds\")   This patch (of 3):  When the second-stage kernel is booted with a limiting command line (e.g.  \"mem=\u003csize\u003e\"), the IMA measurement buffer handed over from the previous kernel may fall outside the addressable RAM of the new kernel.  Accessing such a buffer can fault during early restore.  Introduce a small generic helper, ima_validate_range(), which verifies that a physical [start, end] range for the previous-kernel IMA buffer lies within addressable memory: \t- On x86, use pfn_range_is_mapped(). \t- On OF based architectures, use page_is_ram().",
  "id": "DEBIAN-CVE-2026-43129",
  "modified": "2026-09-14T16:47:29.265696530Z",
  "published": "2026-05-06T12:16:29.963Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-43129"
    }
  ],
  "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-43129"
  ]
}