Homepage

CVE-2026-31413 Affecting kernel-uek64k-modules-wireless package, versions <0:6.12.0-202.76.4.1.el10uek

Severity

 Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE10-KERNELUEK64KMODULESWIRELESS-16692448
  • published14 May 2026
  • disclosed12 Apr 2026
Report a new vulnerability Found a mistake?

Introduced: 12 Apr 2026

CVE-2026-31413  (opens in a new tab)

How to fix?

Upgrade Oracle:10 kernel-uek64k-modules-wireless to version 0:6.12.0-202.76.4.1.el10uek or higher.
This issue was patched in ELSA-2026-50260.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-uek64k-modules-wireless package and not the kernel-uek64k-modules-wireless package as distributed by Oracle. See How to fix? for Oracle:10 relevant fixed versions and status.

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR

maybe_fork_scalars() is called for both BPF_AND and BPF_OR when the source operand is a constant. When dst has signed range [-1, 0], it forks the verifier state: the pushed path gets dst = 0, the current path gets dst = -1.

For BPF_AND this is correct: 0 & K == 0. For BPF_OR this is wrong: 0 | K == K, not 0.

The pushed path therefore tracks dst as 0 when the runtime value is K, producing an exploitable verifier/runtime divergence that allows out-of-bounds map access.

Fix this by passing env->insn_idx (instead of env->insn_idx + 1) to push_stack(), so the pushed path re-executes the ALU instruction with dst = 0 and naturally computes the correct result for any opcode.