CVE-2026-68135

net: hip04: fix RX buffer leak on build_skb failure

N/A

Published: August 10, 2026 at 11:58 AM UTC

Updated: August 19, 2026 at 05:20 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

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.

Affected

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

Linux Kernel · Linux

95%

4.5 ≤ v < 5.10.2654.5 ≤ v < 5.15.2164.5 ≤ v < 6.1.1834.5 ≤ v < 6.12.1014.5 ≤ v < 6.18.424.5 ≤ v < 6.6.1484.5 ≤ v < 7.1.64.5 ≤ v < 7.24.5701a0fd5231866db08cebcd502894699f49cb960

Vendor states this is fixed in 14fa65d10f5696b063a7d8d26e8291ea84a2c6ed (fixed)

Vendor states this is fixed in 2b19fe277645fd1aeb18fd4ecdcf31966080dee7 (fixed)

Vendor states this is fixed in 67a7614bde310da006ab259f4f163d3fb0f9e253 (fixed)

Vendor states this is fixed in 690ecc13a4032e5cae1dc6659512f32b033533b0 (fixed)

Vendor states this is fixed in 80d977f280b4eccd4ac5369871d0ecb2b9c9a49d (fixed)

Vendor states this is fixed in a0f247d63489a107bbc3b712a77b302af2a2a173 (fixed)

Vendor states this is fixed in bcd43ee1f25b682151df213c06a99b2e1c1cf2e5 (fixed)

Vendor states this is fixed in e054dcd990d8180cde529ea28ce0838e76a5ad5e (fixed)

Vendor states this is fixed in 4.5 (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)