Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-43009: bpf: Fix incorrect pruning due to atomic fetch precision tracking

Noroxi assessment

Priority: Monitor (action score 31/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.16% (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 06999c8a2c52b13977771ab093b8e179821b532d, 179ee84a89114b854ac2dd1d293633a7f6c8dac1, 1aac6b271e0a80b91c2f6a8f75ab0c0b1fc8ffe8; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 06999c8a2c52b13977771ab093b8e179821b532d, 179ee84a89114b854ac2dd1d293633a7f6c8dac1, 1aac6b271e0a80b91c2f6a8f75ab0c0b1fc8ffe8; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: bpf: Fix incorrect pruning due to atomic fetch precision tracking When backtrack_insn encounters a BPF_STX instruction with BPF_ATOMIC and BPF_FETCH, the src register (or r0 for BPF_CMPXCHG) also acts as a destination, thus receiving the old value from the memory location. The current backtracking logic does not account for this. It treats atomic fetch operations the same as regular stores where the src register is only an input. This leads the backtrack_insn to fail to propagate precision to the stack location, which is then not marked as precise! Later, the verifier's path pruning can incorrectly consider two states equivalent when they differ in terms of stack state. Meaning, two branches can be treated as equivalent and thus get pruned when they should not be seen as such. Fix it as follows: Extend the BPF_LDX handling in backtrack_insn to also cover atomic fetch operations via is_atomic_fetch_insn() helper. When the fetch dst register is being tracked for precision, clear it, and propagate precision over to the stack slot. For non-stack memory, the precision walk stops at the atomic instruction, same as regular BPF_LDX. This covers all fetch variants. Before: 0: (b7) r1 = 8 ; R1=8 1: (7b) *(u64 *)(r10 -8) = r1 ; R1=8 R10=fp0 fp-8=8 2: (b7) r2 = 0 ; R2=0 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) ; R2=8 R10=fp0 fp-8=mmmmmmmm 4: (bf) r3 = r10 ; R3=fp0 R10=fp0 5: (0f) r3 += r2 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r2 stack= before 4: (bf) r3 = r10 mark_precise: frame0: regs=r2 stack= before 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) mark_precise: frame0: regs=r2 stack= before 2: (b7) r2 = 0 6: R2=8 R3=fp8 6: (b7) r0 = 0 ; R0=0 7: (95) exit After: 0: (b7) r1 = 8 ; R1=8 1: (7b) *(u64 *)(r10 -8) = r1 ; R1=8 R10=fp0 fp-8=8 2: (b7) r2 = 0 ; R2=0 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) ; R2=8 R10=fp0 fp-8=mmmmmmmm 4: (bf) r3 = r10 ; R3=fp0 R10=fp0 5: (0f) r3 += r2 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r2 stack= before 4: (bf) r3 = r10 mark_precise: frame0: regs=r2 stack= before 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) mark_precise: frame0: regs= stack=-8 before 2: (b7) r2 = 0 mark_precise: frame0: regs= stack=-8 before 1: (7b) *(u64 *)(r10 -8) = r1 mark_precise: frame0: regs=r1 stack= before 0: (b7) r1 = 8 6: R2=8 R3=fp8 6: (b7) r0 = 0 ; R0=0 7: (95) exit

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 1, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-43009

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 kernel5.12 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

    • 5.12affected
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before 06999c8a2c52b13977771ab093b8e179821b532daffected · git
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before 1aac6b271e0a80b91c2f6a8f75ab0c0b1fc8ffe8affected · git
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before 7c72e5f3741d1c5cc53439137162f0e09254e6e9affected · git
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before ea150ffa9fc9f78c5cf22e1f7b06b6d016b1017caffected · git
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before 7ffbe45b1d227e24659998a91cfd4c27af457e71affected · git
    • 5ca419f2864a2c60940dcf4bbaeb69546200e36f and later · before 179ee84a89114b854ac2dd1d293633a7f6c8dac1affected · git
    • before 5.12not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.160 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:14linuxbefore 6.19.12-16.19.12-1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.34.1.160000.2.156.12.0-160000.34.1.160000.2.15
SUSE:Linux Micro 6.2kernel-rtbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro 6.2kernel-sourcebefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro Extras 6.2kernel-obs-buildbefore 6.12.0-160000.34.16.12.0-160000.34.1
SUSE:Linux Micro Extras 6.2kernel-symsbefore 6.12.0-160000.34.16.12.0-160000.34.1

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-31777May 1, 2026 · ALSA: ctxfi: Check the error for index mapping
    22Monitor
  • ← EarlierCVE-2026-31779May 1, 2026 · wifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler()
    32Monitor
  • Later →CVE-2026-43010May 1, 2026 · bpf: Reject sleepable kprobe_multi programs at attach time
    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 Linux06999c8a2c52b13977771ab093b8e179821b532dVendor (CNA)
Linux Linux179ee84a89114b854ac2dd1d293633a7f6c8dac1Vendor (CNA)
Linux Linux1aac6b271e0a80b91c2f6a8f75ab0c0b1fc8ffe8Vendor (CNA)
Linux Linux7c72e5f3741d1c5cc53439137162f0e09254e6e9Vendor (CNA)
Linux Linux7ffbe45b1d227e24659998a91cfd4c27af457e71Vendor (CNA)
Linux Linuxea150ffa9fc9f78c5cf22e1f7b06b6d016b1017cVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.19.12-1 · Debian:14Package registry (OSV)
suse:kernel-64kb6.12.0-160000.34.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.34.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.34.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.34.1.160000.2.15 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.34.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.34.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.34.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.34.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.34.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.34.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.34.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-zfcpdump6.12.0-160000.34.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.

  • CVE-2026-4598826 days apartrxrpc: Fix re-decryption of RESPONSE packets
    39Monitor
  • CVE-2026-4624433 days apartnetfilter: nft_inner: Fix IPv6 inner_thoff desync
    36Monitor
  • CVE-2026-5321755 days apartnet: mvpp2: sync RX data at the hardware packet offset
    34Monitor
  • CVE-2026-5292054 days apartnetfilter: xt_policy: fix strict mode inbound policy matching
    33Monitor
  • CVE-2026-6417679 days apartwifi: iwlwifi: mvm: fix driver-set TX rates on old devices
    32Monitor
  • CVE-2026-430300 days apartbpf: Fix regsafe() for pointers to packet
    31Monitor

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-secondary

Attack context

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

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records