# CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure

> A resource leak in the hip04 network driver allows remote attackers to cause a denial of service by triggering build_skb failures.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68135, DEBIAN-CVE-2026-68135, GHSA-46mx-vfg9-j7vh, UBUNTU-CVE-2026-68135

## What is CVE-2026-68135?

CVE-2026-68135 is a denial of service vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

net: hip04: fix RX buffer leak on build_skb failure

When build_skb() fails in hip04_rx_poll(), the driver jumps to the
refill path without releasing the current RX buffer and its DMA mapping.
Installing a replacement buffer then overwrites the slot references and
leaks both resources.

Keep the current slot intact and return budget so NAPI retries the same
buffer.  Also free a newly allocated RX fragment when dma_map_single()
fails.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-68135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68135 is a denial of service vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68135 in the wild and no public exploit code.

Affected product: Linux. 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-68135/ (Markdown: https://insights.sbomify.com/CVE-2026-68135/index.md)
```

## Sources

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

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