CVE ID : CVE-2025-68725<\/p>\n
Published : Dec. 24, 2025, 11:16 a.m. | 1\u00a0hour, 5\u00a0minutes ago<\/p>\n
Description : In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
bpf: Do not let BPF test infra emit invalid GSO types to stack<\/p>\n
Yinhao et al. reported that their fuzzer tool was able to trigger a
\nskb_warn_bad_offload() from netif_skb_features() -> gso_features_check().
\nWhen a BPF program – triggered via BPF test infra – pushes the packet
\nto the loopback device via bpf_clone_redirect() then mentioned offload
\nwarning can be seen. GSO-related features are then rightfully disabled.<\/p>\n
We get into this situation due to convert___skb_to_skb() setting
\ngso_segs and gso_size but not gso_type. Technically, it makes sense
\nthat this warning triggers since the GSO properties are malformed due
\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy
\nthrough setting it at least to SKB_GSO_DODGY without any other specific
\nassumptions, but that also feels wrong given we should not go further
\ninto the GSO engine in the first place.<\/p>\n
The checks were added in 121d57af308d (“gso: validate gso_type in GSO
\nhandlers”) because there were malicious (syzbot) senders that combine
\na protocol with a non-matching gso_type. If we would want to drop such
\npackets, gso_features_check() currently only returns feature flags via
\nnetif_skb_features(), so one location for potentially dropping such skbs
\ncould be validate_xmit_unreadable_skb(), but then otoh it would be
\nan additional check in the fast-path for a very corner case. Given
\nbpf_clone_redirect() is the only place where BPF test infra could emit
\nsuch packets, lets reject them right there.<\/p>\n
Severity: 0.0 | NA<\/p>\n
Visit the link for more details, such as CVSS details, affected products, timeline, and more…\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"
CVE ID : CVE-2025-68725 Published : Dec. 24, 2025, 11:16 a.m. | 1\u00a0hour, 5\u00a0minutes ago Description : In the Linux kernel, the following vulnerability has been resolved: bpf: Do not let BPF test infra emit invalid GSO types to stack Yinhao et al. reported that their fuzzer tool was able to trigger a skb_warn_bad_offload() from …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-74824","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/74824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=74824"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/74824\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=74824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=74824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=74824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}