CVE-2026-43321: bpf: Properly mark live registers for indirect jumps
In the Linux kernel, the following vulnerability has been resolved:
bpf: Properly mark live registers for indirect jumps
For a `gotox rX` instruction the rX register should be marked as used
in the compute_insn_live_regs() function. Fix this.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43321 is a Linux kernel BPF bug fixed in stable kernel commits. It is rated high because a local, low-privileged user could potentially affect confidentiality, integrity, and availability. There is no provided evidence of active exploitation or KEV listing. Organizations running affected Linux kernels should prioritize vendor kernel updates.
Executive priority
Treat as a near-term patching priority for Linux fleets, especially shared compute and container hosts. It is not described as remotely exploitable in the supplied sources, but the potential local impact is high. Prioritize validation and vendor kernel updates over emergency internet-edge response.
Technical view
The issue is in Linux kernel BPF live-register analysis for indirect jump instructions: gotox rX did not properly mark rX as used in compute_insn_live_regs(). The published CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact. The source lists Linux 6.19-related affected versions and two kernel stable fix commits.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions where local users or workloads can reach BPF functionality. Internet-facing status alone is not the key factor; local access or compromised workloads matter. The affected-version data is limited, so validate against distribution advisories.
Exploitation context
The provided sources do not state active exploitation, public exploit availability, or KEV inclusion. CVSS indicates exploitation requires local privileges and no user interaction. Container, multi-user, CI, and shared-host environments may have higher practical concern if untrusted users can execute code locally.
Researcher notes
Evidence is sparse beyond the kernel fix description and CVSS. The affected-version listing appears limited and should not be treated as a complete distribution matrix. The key code area is BPF verifier or analysis handling of live registers for indirect gotox rX jumps.
Mitigation direction
Apply Linux kernel updates from your distribution when available.
Prefer kernels containing the referenced upstream stable fix commits.
Check vendor advisories for exact affected and fixed package versions.
Reduce local access for untrusted users where feasible.
Review BPF exposure according to distribution hardening guidance.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and containers hosts.
Map installed kernel packages to vendor advisories for CVE-2026-43321.
Confirm whether running kernels include the referenced stable commits.
Identify systems allowing untrusted local users or workloads.
Track remediation until rebooted systems run fixed kernels.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43321 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.