CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments()
In the Linux kernel, the following vulnerability has been resolved:
x86/kexec: Disable KCOV instrumentation after loadsegments()
The loadsegments() function changes segment registers, invalidating GS base (which KCOV relies on for per-cpu data). When CONFIGKCOV is enabled, any subsequent instrumented C code call (e.g. nativegdtinvalidate()) 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 CONFIGKEXEC and CONFIGKCOV to be enabled simultaneously.
Adding safeguards directly to the KCOV fast-path (sanitizercovtracepc()) 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 machinekexec64.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 CONFIGKCOV is not supported there.
[ bp: Space out comment for better readability. ]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Disable KCOV instrumentation for the entire machine_kexec_64.c and for subsequent instrumented C code calls so that KCOV is not active after load_segments() (i.e., ensure KCOV instrumentation is turned off in machine_kexec_64.c to avoid invoking __sanitizer_cov_trace_pc() after load_segments()).
x86 kexec (machine_kexec_64.c) KCOV instrumentation = disabled - Configuration
Add safeguards directly to the KCOV fast-path (__sanitizer_cov_trace_pc()) to prevent unsafe per-CPU data access when segment registers (GS base) are changed by load_segments().
KCOV fast-path __sanitizer_cov_trace_pc() safeguards = added
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43331?
CVE-2026-43331 has been classified with a moderate severity rating due to its potential impact on security within the Linux kernel.
How do I fix CVE-2026-43331?
To mitigate CVE-2026-43331, users should upgrade to the latest version of the Linux kernel where the vulnerability has been resolved.
Which versions of the Linux kernel are affected by CVE-2026-43331?
CVE-2026-43331 affects versions of the Linux kernel that utilize the x86_64 architecture, particularly prior to the patch.
What are the risks associated with CVE-2026-43331?
The primary risk associated with CVE-2026-43331 is the potential for exploitation that may lead to unauthorized access or control over system resources.
Does CVE-2026-43331 affect all Linux distributions?
CVE-2026-43331 impacts any Linux distributions that incorporate the vulnerable x86_64 kernel version unless patched.