CVE-2025-68363bpf: Check skb->transport_header is set in bpf_skb_check_mtu
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 8 days later
· 8 days later
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < b3171a5e4622e915e94599a55f4964078bdec27e
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < 97b876fa88322625228792cf7a5fd77531815a80
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < 30ce906557a21adef4cba5901c8e995dc18263a9
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < 1c30e4afc5507f0069cc09bd561e510e4d97fbf7
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < 942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5
- affected 34b2021cc61642d61c3cf943d9e71925b827941b – < d946f3c98328171fa50ddb908593cf833587f725
- affected 5.12
- unaffected < 5.12
- unaffected 6.1.160 – ≤ 6.1.*
- unaffected 6.6.120 – ≤ 6.6.*
- unaffected 6.12.63 – ≤ 6.12.*
- unaffected 6.17.13 – ≤ 6.17.*
- unaffected 6.18.2 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References8
- https://git.kernel.org/stable/c/b3171a5e4622e915e94599a55f4964078bdec27e (opens in a new tab)
- https://git.kernel.org/stable/c/97b876fa88322625228792cf7a5fd77531815a80 (opens in a new tab)
- https://git.kernel.org/stable/c/30ce906557a21adef4cba5901c8e995dc18263a9 (opens in a new tab)
- https://git.kernel.org/stable/c/1c30e4afc5507f0069cc09bd561e510e4d97fbf7 (opens in a new tab)
- https://git.kernel.org/stable/c/942268e2726ac7f16e3ec49dbfbbbe7cf5af9da5 (opens in a new tab)
- https://git.kernel.org/stable/c/d946f3c98328171fa50ddb908593cf833587f725 (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-205091 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68363)Record last updated .