PoC Monitor
← All CVEs
CVE-2026-31413published 12 Apr 2026 05:36 UTCData: JSON · API

Linux

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

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.

First public PoC 5 hafter publication · 12 Apr 2026
Public PoCs11 on GitHub
CVSS7.8high · scored by CNA · CWE-125
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= dea9989a3f3961faede93752cd81eb5a9514d911, < 342aa1ee995ef5bbf876096dc3a5e51218d76fa4
  • >= 4c122e8ae14950cf6b59d208fc5160f7c601e746, < 58bd87d0e69204dbd739e4387a1edb0c4b1644e7
  • >= e52567173ba86dbffb990595fbe60e2e83899372, < d13281ae7ea8902b21d99d10a2c8caf0bdec0455
  • >= bffacdb80b93b7b5e96b26fad64cc490a6c7d6c7, < c845894ebd6fb43226b3118d6b017942550910c5

Fixed in 342aa1ee995ef5bbf876096dc3a5e51218d76fa4, 58bd87d0e69204dbd739e4387a1edb0c4b1644e7, d13281ae7ea8902b21d99d10a2c8caf0bdec0455, c845894ebd6fb43226b3118d6b017942550910c5

Linux Linux
  • >= 6.12.75, < 6.12.80
  • >= 6.18.16, < 6.18.21
  • >= 6.19.6, < 6.19.11

Fixed in 6.12.80, 6.18.21, 6.19.11

Mitigation

Upgrade Linux to 342aa1ee995ef5bbf876096dc3a5e51218d76fa4 or 58bd87d0e69204dbd739e4387a1edb0c4b1644e7 or d13281ae7ea8902b21d99d10a2c8caf0bdec0455 or c845894ebd6fb43226b3118d6b017942550910c5 or later.

Upgrade Linux to 6.12.80 or 6.18.21 or 6.19.11 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published12 Apr 2026 · t = 0First public PoC12 Apr 2026 · t+5h

First public PoC 5 h after publication; not in CISA KEV. First PoC: Rat5ak/CVE-2026-31413-BPF-Container-Escape (created 12 Apr 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
Rat5ak/CVE-2026-31413-BPF-Container-Escape 12 Apr 2026 +5 h 1 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.