Security readout for executives and security teams
Plain-English summary
A flaw in the Linux BPF verifier can incorrectly treat two registers as having the same safe value after a byte-swap operation. A local, low-privileged attacker could potentially use this mistaken validation to access memory outside permitted bounds, threatening confidentiality, integrity, and availability.
Executive priority
Treat as a high-priority kernel update for systems permitting untrusted local access. Accelerate remediation on shared servers, development platforms, and other environments where low-privileged users may reach BPF. There is no supplied evidence of active exploitation, so urgency should be exposure-driven rather than treated as an ongoing emergency.
Technical view
BPF_END mutates a scalar register but failed to clear its shared scalar ID. A later conditional check could therefore propagate bounds from the changed register to another register still carrying that ID. The verifier might approve unsafe BPF behavior, potentially enabling out-of-bounds memory access. The cited kernel fixes reset the destination register ID.
Likely exposure
Exposure is limited to Linux systems running a vulnerable kernel where a low-privileged local user can reach the affected BPF verifier path. The bundle does not provide reliable affected-version ranges; its listed versions and commits are marked with a default status of unaffected. Confirm applicability with the kernel or distribution vendor.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high impact across confidentiality, integrity, and availability. The bundle reports KEV as false and provides no evidence of active exploitation or a public exploit.
Researcher notes
The core invariant failure is stale scalar-ID aliasing after in-place BPF_END transformation. Clearing dst_reg->id breaks the relationship and prevents unsafe bound propagation. The source bundle does not establish introduction commits, complete vulnerable ranges, exploitability under specific BPF privilege configurations, or affected distribution packages; those require vendor confirmation.
Mitigation direction
- Apply vendor-supported kernel updates containing the cited BPF verifier correction.
- Check Linux distribution advisories for package-specific fixed versions and reboot requirements.
- Prioritize multi-user or otherwise untrusted systems where local users can access BPF functionality.
- Use vendor-recommended temporary mitigations if immediate kernel updating is unavailable.
Validation and detection
- Record the running kernel version and distribution package release on each Linux system.
- Confirm with the distribution vendor whether each deployed kernel build is affected.
- Verify the installed kernel incorporates an applicable cited stable fix.
- After updating and rebooting, confirm the fixed kernel is running.
- Review local BPF access controls to identify systems with greater reachable exposure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-43070 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/a17443af874229408ce6b78e2c8a2b5adeb4b7d8CVE reference, Linux
- https://git.kernel.org/stable/c/0d15c3611a2cc5d08993545d4032055ae10ae2c1CVE reference, Linux
- https://git.kernel.org/stable/c/a3125bc01884431d30d731461634c8295b6f0529CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.