Linux Kernel up to 6.12.79/6.18.20/6.19.10/7.0-rc4 bpf bpf_jit_blind_insn privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.4$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.12.79/6.18.20/6.19.10/7.0-rc4. This affects the function bpf_jit_blind_insn of the component bpf. The manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2026-23417. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.79/6.18.20/6.19.10/7.0-rc4 and classified as critical. This issue affects the function bpf_jit_blind_insn of the component bpf. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix constant blinding for PROBE_MEM32 stores BPF_ST | BPF_PROBE_MEM32 immediate stores are not handled by bpf_jit_blind_insn(), allowing user-controlled 32-bit immediates to survive unblinded into JIT-compiled native code when bpf_jit_harden >= 1. The root cause is that convert_ctx_accesses() rewrites BPF_ST|BPF_MEM to BPF_ST|BPF_PROBE_MEM32 for arena pointer stores during verification, before bpf_jit_blind_constants() runs during JIT compilation. The blinding switch only matches BPF_ST|BPF_MEM (mode 0x60), not BPF_ST|BPF_PROBE_MEM32 (mode 0xa0). The instruction falls through unblinded. Add BPF_ST|BPF_PROBE_MEM32 cases to bpf_jit_blind_insn() alongside the existing BPF_ST|BPF_MEM cases. The blinding transformation is identical: load the blinded immediate into BPF_REG_AX via mov+xor, then convert the immediate store to a register store (BPF_STX). The rewritten STX instruction must preserve the BPF_PROBE_MEM32 mode so the architecture JIT emits the correct arena addressing (R12-based on x86-64). Cannot use the BPF_STX_MEM() macro here because it hardcodes BPF_MEM mode; construct the instruction directly instead.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-23417 since 01/13/2026. The exploitation is known to be difficult. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/24/2026).

The vulnerability scanner Nessus provides a plugin with the ID 318102 (openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20826-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.80, 6.18.21, 6.19.11 or 7.0-rc5 eliminates this vulnerability. Applying the patch 56af722756ed82fee2ae5d5b4d04743407506195/ccbf29b28b5554f9d65b2fb53b994673ad58b3bf/de641ea08f8fff6906e169d2576c2ac54e562fbb/2321a9596d2260310267622e0ad8fbfa6f95378f is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (318102), EUVD (EUVD-2026-18200) and CERT Bund (WID-SEC-2026-0985). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Microsoft Azure Linux

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.4

VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 318102
Nessus Name: openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20826-1)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.80/6.18.21/6.19.11/7.0-rc5
Patch: 56af722756ed82fee2ae5d5b4d04743407506195/ccbf29b28b5554f9d65b2fb53b994673ad58b3bf/de641ea08f8fff6906e169d2576c2ac54e562fbb/2321a9596d2260310267622e0ad8fbfa6f95378f

Timelineinfo

01/13/2026 CVE reserved
04/02/2026 +78 days Advisory disclosed
04/02/2026 +0 days VulDB entry created
06/24/2026 +83 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23417 (🔒)
GCVE (CVE): GCVE-0-2026-23417
GCVE (VulDB): GCVE-100-354857
EUVD: 🔒
CERT Bund: WID-SEC-2026-0985 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/02/2026 14:22
Updated: 06/24/2026 22:19
Changes: 04/02/2026 14:22 (58), 04/02/2026 15:51 (1), 04/08/2026 01:25 (7), 05/11/2026 16:24 (1), 06/02/2026 04:51 (2), 06/24/2026 22:19 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!