CVE-2026-98151— bpf: Fix REG INVARIANTS VIOLATION on speculative pointer arithmetic
Quick assessment
Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
在 Linux 内核中，已修复以下漏洞： BPF：修复推测性指针算术操作中的 REG INVARIANTS（寄存器不变量）违规 以下面的非特权 BPF 程序为例： 加载该程序会触发 发出的验证器警告： 问题成因分析： 1. 在处理指令 14（ ）时， 函数会计算新的偏移量，并将其写入目标寄存器（dst_reg）的 以及 32/64 位范围信息中。 2. 由于指针寄存器不跟踪 32 位子寄存器的边界， 函数首先将 设置为完整范围（full range）。随后，在函数结束时， 会根据偏移量重新推导 的值。 3. 在非特
Possible ATT&CK Techniques 1 AI
T1206Affected Version Matrix 10
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 5f99f312bd3bedb3b266b0d26376a8c500cdc97f< 21a681526c715aebb4f918b8c131583442d1b3d8 |
affected |
5f99f312bd3bedb3b266b0d26376a8c500cdc97f< d623a4a58bb238443505d5c2949d1182dcfc26b6 |
affected | ||
5f99f312bd3bedb3b266b0d26376a8c500cdc97f< 9f9477ae73de9c5a28e8ab7000d8097b078faee4 |
affected | ||
5f99f312bd3bedb3b266b0d26376a8c500cdc97f< 150aeba624e8b7cac51c39440d7e8e1fd11de9a0 |
affected | ||
6.8 |
affected | ||
< 6.8 |
unaffected | ||
6.12.111≤ 6.12.* |
unaffected | ||
6.18.53≤ 6.18.* |
unaffected | ||
| … +2 more rows | |||
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-98151
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
bpf: Fix REG INVARIANTS VIOLATION on speculative pointer arithmetic
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix REG INVARIANTS VIOLATION on speculative pointer arithmetic
Take the following unprivileged program as an example:
r0 = bpf_map_lookup_elem(...) /* PTR_TO_MAP_VALUE, offset 0 */
...
14: r0 += r1 /* r1 is a bounded scalar */
15: r9 = r0
Loading it triggers a verifier warning from reg_bounds_sanity_check():
verifier bug: REG INVARIANTS VIOLATION (alu): const subreg tnum out
of sync with range bounds r64={.base=0x0, .size=0x0}
r32={.base=0x0, .size=0xffffffff} var_off=(0x0, 0x0)
What happens:
1. Processing insn 14 (r0 += r1) in adjust_ptr_min_max_vals(), the new
offset is computed into dst_reg's var_off and 32/64-bit ranges.
2. Because pointer registers do not track 32-bit subregister bounds,
__mark_reg32_unbounded() first sets r32 to the full range; r32 is
re-derived from the offset at the end of the function by
reg_bounds_sync().
3. On the unprivileged path, sanitize_ptr_alu() is called and, via
sanitize_speculative_path() -> push_stack(), snapshots the current
register state and schedules the next instruction (insn 15) to be
verified directly as a speculative path.
4. That snapshot is taken between step 2 and the final reg_bounds_sync():
at this point dst_reg's var_off still holds the (const) original
offset while r32 has just been blanked to the full range, i.e. the two
are out of sync. When the speculative path later verifies insn 15
(r9 = r0), the inconsistent state reaches reg_bounds_sanity_check() and
trips the warning.
var_off and the 32-bit range must always be consistent. There are two
ways to keep the snapshot consistent:
1. sync var_off and r32 before the snapshot so they match, or
2. leave r32 at its original (already consistent) value and blank it
only after the snapshot.
The whole point of sanitize_ptr_alu() is to insert a harmless masking
sequence that keeps the access in bounds under speculation, so the state
it snapshots should faithfully represent that. Take approach 2: move
__mark_reg32_unbounded() to after sanitize_ptr_alu(), so the speculative
snapshot keeps the pointer's original, consistent r32. The non-speculative
path is unchanged: r32 is still blanked before the offset is applied and
re-derived by reg_bounds_sync().
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Affected Products
II. Public POCs for CVE-2026-98151
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-98151
请登录查看更多情报信息。
Patches & Fixes for CVE-2026-98151 (4)
Same Patch Batch · Linux · 2026-09-25 · 372 CVEs total
| CVE-2026-100075 | 9.8 CRITICAL | RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters |
| CVE-2026-97555 | 8.8 HIGH | smb: client: fix heap overflow in DACL owner/group rewrite |
| CVE-2026-97957 | 8.8 HIGH | net: hinic: fix mailbox segment buffer overflow |
| CVE-2026-97527 | 8.8 HIGH | scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock |
| CVE-2026-97528 | 8.8 HIGH | scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error |
| CVE-2026-98115 | 8.8 HIGH | ksmbd: safely drain sessions during logoff |
| CVE-2026-97525 | 8.2 HIGH | x86/mm/pat: Allocate split page tables as kernel page tables |
| CVE-2026-98069 | 8.1 HIGH | net/rds: acquire the fastpath locks in rds_conn_shutdown() |
| CVE-2026-97573 | 8.1 HIGH | bnxt_en: Handle buffer allocation failure in bnxt_rx_ring_reset() |
| CVE-2026-97570 | 8.1 HIGH | bnxt_en: Bound SW TPA IDs to prevent crashes |
| CVE-2026-98130 | 8.1 HIGH | sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START |
| CVE-2026-98070 | 8.1 HIGH | net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() |
| CVE-2026-98122 | 7.8 HIGH | vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() |
| CVE-2026-97575 | 7.8 HIGH | media: v4l2-ctrls: validate AV1 tile counts |
| CVE-2026-97576 | 7.8 HIGH | media: v4l2-ctrls: validate HEVC tile counts |
| CVE-2026-97941 | 7.8 HIGH | mm/slab: take n->list_lock in __slab_try_return_freelist() to avoid race |
| CVE-2026-98112 | 7.8 HIGH | ksmbd: fix listener task lifetime on netdev events |
| CVE-2026-98116 | 7.8 HIGH | ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF |
| CVE-2026-97580 | 7.8 HIGH | media: rkvdec: bound HEVC tile loops and PPS id to the array capacity |
| CVE-2026-97940 | 7.8 HIGH | ipv6: fix fib6 walker UAF on seq stop |
Showing top 20 of 372 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
-
CVE-2026-98384
bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destr -
CVE-2026-98383
bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL -
CVE-2026-98382
bpf: Reject dev-bound-only programs on other devices -
CVE-2026-98381
veth: manage XDP program pointers during channel resize -
CVE-2026-98380
net/sched: reject IDR error pointers when deleting actions
Same vendor: Linux
-
CVE-2026-98384
bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destr -
CVE-2026-98383
bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL -
CVE-2026-98382
bpf: Reject dev-bound-only programs on other devices -
CVE-2026-98381
veth: manage XDP program pointers during channel resize -
CVE-2026-98380
net/sched: reject IDR error pointers when deleting actions
V. Comments for CVE-2026-98151
No comments yet