# CVE-2026-53090: bpf: Fix ld_{abs,ind} failure path analysis in subprogs

> The Linux kernel BPF verifier failed to simulate abnormal exit paths for packet load instructions in subprograms, potentially leading to incorrect program validation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-90374, BELL-CVE-2026-53090, DEBIAN-CVE-2026-53090, GHSA-h443-hx93-m7qc, ROOT-OS-DEBIAN-11-CVE-2026-53090, ROOT-OS-DEBIAN-12-CVE-2026-53090, ROOT-OS-DEBIAN-13-CVE-2026-53090, ROOT-OS-UBUNTU-2204-CVE-2026-53090, ROOT-OS-UBUNTU-2404-CVE-2026-53090, UBUNTU-CVE-2026-53090

## What is CVE-2026-53090?

CVE-2026-53090 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-253 (Incorrect Check of Function Return Value)

## Which versions are affected by CVE-2026-53090?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53090?

Apply the vendor's patch.

## Is CVE-2026-53090 being exploited?

There is no known exploitation of CVE-2026-53090 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53090 and fix it if it is affected.

What it is: CVE-2026-53090 is a high-severity vulnerability in Linux kernel, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53090 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53090/ (Markdown: https://insights.sbomify.com/CVE-2026-53090/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53090
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53090
- OSV: https://osv.dev/vulnerability/CVE-2026-53090

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53090/
Summaries are generated and may contain mistakes; the official description above is the record.