CVE-2026-43331 (GCVE-0-2026-43331)

Vulnerability from cvelistv5 – Published: 2026-05-08 13:31 – Updated: 2026-06-19 11:58
VLAI
Title
x86/kexec: Disable KCOV instrumentation after load_segments()
Summary
In the Linux kernel, the following vulnerability has been resolved: x86/kexec: Disable KCOV instrumentation after load_segments() The load_segments() function changes segment registers, invalidating GS base (which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any subsequent instrumented C code call (e.g. native_gdt_invalidate()) begins crashing the kernel in an endless loop. To reproduce the problem, it's sufficient to do kexec on a KCOV-instrumented kernel: $ kexec -l /boot/otherKernel $ kexec -e The real-world context for this problem is enabling crash dump collection in syzkaller. For this, the tool loads a panic kernel before fuzzing and then calls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC and CONFIG_KCOV to be enabled simultaneously. Adding safeguards directly to the KCOV fast-path (__sanitizer_cov_trace_pc()) is also undesirable as it would introduce an extra performance overhead. Disabling instrumentation for the individual functions would be too fragile, so disable KCOV instrumentation for the entire machine_kexec_64.c and physaddr.c. If coverage-guided fuzzing ever needs these components in the future, other approaches should be considered. The problem is not relevant for 32 bit kernels as CONFIG_KCOV is not supported there. [ bp: Space out comment for better readability. ]
Severity
No CVSS data available.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef , < 0e96cd314c0d819c1635d68125a4d77852c2162e (git)
Affected: 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef , < 593d67032544b9271094fc9b43e437e017cb2b2f (git)
Affected: 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef , < 1e3e98596c2769721ade0418434852fb3af4849a (git)
Affected: 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef , < de05c66fab8847237a9ca216934e56d3ee837f08 (git)
Affected: 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef , < 917e3ad3321e75ca0223d5ccf26ceda116aa51e1 (git)
Create a notification for this product.
Linux Linux Affected: 6.6
Unaffected: 0 , < 6.6 (semver)
Unaffected: 6.6.143 , ≤ 6.6.* (semver)
Unaffected: 6.12.93 , ≤ 6.12.* (semver)
Unaffected: 6.18.22 , ≤ 6.18.* (semver)
Unaffected: 6.19.12 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kernel/Makefile",
            "arch/x86/mm/Makefile"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "0e96cd314c0d819c1635d68125a4d77852c2162e",
              "status": "affected",
              "version": "0d345996e4cb573f8cc81d49b3ee9a7fd2035bef",
              "versionType": "git"
            },
            {
              "lessThan": "593d67032544b9271094fc9b43e437e017cb2b2f",
              "status": "affected",
              "version": "0d345996e4cb573f8cc81d49b3ee9a7fd2035bef",
              "versionType": "git"
            },
            {
              "lessThan": "1e3e98596c2769721ade0418434852fb3af4849a",
              "status": "affected",
              "version": "0d345996e4cb573f8cc81d49b3ee9a7fd2035bef",
              "versionType": "git"
            },
            {
              "lessThan": "de05c66fab8847237a9ca216934e56d3ee837f08",
              "status": "affected",
              "version": "0d345996e4cb573f8cc81d49b3ee9a7fd2035bef",
              "versionType": "git"
            },
            {
              "lessThan": "917e3ad3321e75ca0223d5ccf26ceda116aa51e1",
              "status": "affected",
              "version": "0d345996e4cb573f8cc81d49b3ee9a7fd2035bef",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kernel/Makefile",
            "arch/x86/mm/Makefile"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.6"
            },
            {
              "lessThan": "6.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.143",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.93",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.22",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.12",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.143",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.93",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.22",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.12",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/kexec: Disable KCOV instrumentation after load_segments()\n\nThe load_segments() function changes segment registers, invalidating GS base\n(which KCOV relies on for per-cpu data). When CONFIG_KCOV is enabled, any\nsubsequent instrumented C code call (e.g. native_gdt_invalidate()) begins\ncrashing the kernel in an endless loop.\n\nTo reproduce the problem, it\u0027s sufficient to do kexec on a KCOV-instrumented\nkernel:\n\n  $ kexec -l /boot/otherKernel\n  $ kexec -e\n\nThe real-world context for this problem is enabling crash dump collection in\nsyzkaller. For this, the tool loads a panic kernel before fuzzing and then\ncalls makedumpfile after the panic. This workflow requires both CONFIG_KEXEC\nand CONFIG_KCOV to be enabled simultaneously.\n\nAdding safeguards directly to the KCOV fast-path (__sanitizer_cov_trace_pc())\nis also undesirable as it would introduce an extra performance overhead.\n\nDisabling instrumentation for the individual functions would be too fragile,\nso disable KCOV instrumentation for the entire machine_kexec_64.c and\nphysaddr.c. If coverage-guided fuzzing ever needs these components in the\nfuture, other approaches should be considered.\n\nThe problem is not relevant for 32 bit kernels as CONFIG_KCOV is not supported\nthere.\n\n  [ bp: Space out comment for better readability. ]"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-06-19T11:58:29.321Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/0e96cd314c0d819c1635d68125a4d77852c2162e"
        },
        {
          "url": "https://git.kernel.org/stable/c/593d67032544b9271094fc9b43e437e017cb2b2f"
        },
        {
          "url": "https://git.kernel.org/stable/c/1e3e98596c2769721ade0418434852fb3af4849a"
        },
        {
          "url": "https://git.kernel.org/stable/c/de05c66fab8847237a9ca216934e56d3ee837f08"
        },
        {
          "url": "https://git.kernel.org/stable/c/917e3ad3321e75ca0223d5ccf26ceda116aa51e1"
        }
      ],
      "title": "x86/kexec: Disable KCOV instrumentation after load_segments()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-43331",
    "datePublished": "2026-05-08T13:31:18.787Z",
    "dateReserved": "2026-05-01T14:12:56.002Z",
    "dateUpdated": "2026-06-19T11:58:29.321Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-43331",
      "date": "2026-11-19",
      "epss": "0.00122",
      "percentile": "0.02049"
    },
    "microsoft_vex": {
      "current_release_date": "2026-07-02T14:43:42.000Z",
      "cve": "CVE-2026-43331",
      "id": "msrc_CVE-2026-43331",
      "initial_release_date": "2026-05-09T01:02:13.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "product_status:under_investigation": "4",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "x86/kexec: Disable KCOV instrumentation after load_segments()",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-43331.json",
      "version": "7"
    },
    "redhat_vex": {
      "aggregate_severity": "None",
      "current_release_date": "2026-11-07T04:45:02+00:00",
      "cve": "CVE-2026-43331",
      "id": "CVE-2026-43331",
      "initial_release_date": "2026-05-08T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: x86/kexec: Disable KCOV instrumentation after load_segments()",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43331.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.