# CVE-2026-53074: bpf: reject short IPv4/IPv6 inputs in bpf_prog_test_run_skb

> A missing length check in the Linux kernel BPF test run function allows attackers to cause a denial of service via crafted short network packets.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 24 Jun 2026
- **Also known as:** BELL-CVE-2026-53074, DEBIAN-CVE-2026-53074, GHSA-fqx6-8jf8-vfj2, ROOT-OS-DEBIAN-11-CVE-2026-53074, ROOT-OS-DEBIAN-12-CVE-2026-53074, ROOT-OS-UBUNTU-2204-CVE-2026-53074, ROOT-OS-UBUNTU-2404-CVE-2026-53074, UBUNTU-CVE-2026-53074

## What is CVE-2026-53074?

CVE-2026-53074 is a medium-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: reject short IPv4/IPv6 inputs in bpf_prog_test_run_skb

bpf_prog_test_run_skb() calls eth_type_trans() first and then uses
skb->protocol to initialize sk family and address fields for the test
run.

For IPv4 and IPv6 packets, it may access ip_hdr(skb) or ipv6_hdr(skb)
even when the provided test input only contains an Ethernet header.

Reject the input earlier if the Ethernet frame carries IPv4/IPv6
EtherType but the L3 header is too short.

Fold the IPv4/IPv6 header length checks into the existing protocol
switch and return -EINVAL before accessing the network headers.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-53074 being exploited?

There is no known exploitation of CVE-2026-53074 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-53074 and fix it if it is affected.

What it is: CVE-2026-53074 is a medium-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-53074 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-53074/ (Markdown: https://insights.sbomify.com/CVE-2026-53074/index.md)
```

## Sources

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

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