CVE-2026-53090

bpf: Fix ld_{abs,ind} failure path analysis in subprogs

HIGH
7.8
CVSS Score
Published: June 24, 2026 at 04:30 PM UTC
Updated: October 19, 2026 at 08:19 PM UTC
2 products affected across 2 vendorsLinux KernelEnterprise Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10 ≤ v < 7.0.105.109b28d76eac48e922dc293da1aa2b2b85c32aeee
Vendor states this is fixed in 37ad2bb11e9de92cb7b94548705eeedd87f7d392 (fixed)
Vendor states this is fixed in 8674e2db06cff6b50f2216eed9a761d15425bb34 (fixed)
Vendor states this is fixed in 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe (fixed)
Vendor states this is fixed in 928d354ae3557e8f755a227e67be88034eb3cd7f (fixed)
Vendor states this is fixed in ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337 (fixed)
Vendor states this is fixed in d846d83bdacbd8f14fc45c63b8c1d22608452e1c (fixed)
Vendor states this is fixed in de1055e7f9e67af32b1f3376066272b04e5223c0 (fixed)
Vendor states this is fixed in ee861486e377edc55361c08dcbceab3f6b6577bd (fixed)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 6 (unaffected)
Vendor states this is fixed in 7 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (11)

Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-53090
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2492305
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53090.json

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-253NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card