Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments()

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0e96cd314c0d819c1635d68125a4d77852c2162e, 1e3e98596c2769721ade0418434852fb3af4849a, 593d67032544b9271094fc9b43e437e017cb2b2f.

Low priority for now. Upgrade to Linux Linux 0e96cd314c0d819c1635d68125a4d77852c2162e, 1e3e98596c2769721ade0418434852fb3af4849a, 593d67032544b9271094fc9b43e437e017cb2b2f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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. ]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 8, 2026
Updated
Jun 19, 2026
EPSS
0.1% · 1th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43331

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.6 and later · before 6.18.22
  • linux linux kernel6.19 and later · before 6.19.12
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.6affected
    • 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef and later · before 0e96cd314c0d819c1635d68125a4d77852c2162eaffected · git
    • 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef and later · before 593d67032544b9271094fc9b43e437e017cb2b2faffected · git
    • 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef and later · before 1e3e98596c2769721ade0418434852fb3af4849aaffected · git
    • 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef and later · before de05c66fab8847237a9ca216934e56d3ee837f08affected · git
    • 0d345996e4cb573f8cc81d49b3ee9a7fd2035bef and later · before 917e3ad3321e75ca0223d5ccf26ceda116aa51e1affected · git
    • before 6.6not affected · semver
    • 6.6.143 and later · up to and including 6.6.*not affected · semver
    • 6.12.93 and later · up to and including 6.12.*not affected · semver
    • 6.18.22 and later · up to and including 6.18.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.94-16.12.94-1
Debian:14linuxbefore 6.19.12-16.19.12-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.38.1.160000.2.226.12.0-160000.38.1.160000.2.22
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.38.1.160000.2.236.12.0-160000.38.1.160000.2.23
SUSE:Linux Micro 6.2kernel-rtbefore 6.12.0-160000.38.16.12.0-160000.38.1

+3

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43328May 8, 2026 · cpufreq: governor: fix double free in cpufreq_dbs_governor_init() error path
    31Monitor
  • ← EarlierCVE-2026-43330May 8, 2026 · crypto: caam - fix overflow on long hmac keys
    31Monitor
  • Later →CVE-2026-43333May 8, 2026 · bpf: reject direct access to nullable PTR_TO_BUF pointers
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e96cd314c0d819c1635d68125a4d77852c2162eVendor (CNA)
Linux Linux1e3e98596c2769721ade0418434852fb3af4849aVendor (CNA)
Linux Linux593d67032544b9271094fc9b43e437e017cb2b2fVendor (CNA)
Linux Linux917e3ad3321e75ca0223d5ccf26ceda116aa51e1Vendor (CNA)
Linux Linuxde05c66fab8847237a9ca216934e56d3ee837f08Vendor (CNA)
debian:linux6.12.94-1 · Debian:13Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.38.1.160000.2.22 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.38.1.160000.2.23 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.38.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.38.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-zfcpdump6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records