Menu

Star on GitHub · 3.2k

CVE-2026-68135

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 p…

Published Aug 10, 2026EPSS 0.18%

Overview

CVE-2026-68135 is a known-severity vulnerability. It was published on August 10, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-68135?

CVE-2026-68135 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68135?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68135?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68135?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68135 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.