{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.2.8-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  net: skbuff: do not leave stale header offsets after pskb_carve()  pskb_carve_inside_header() and pskb_carve_inside_nonlinear() remove the first bytes of a packet and reallocate skb-\u003ehead.  All the headers that were present before the operation are gone, but both functions call skb_headers_offset_update(skb, 0), which is a no-op : skb-\u003emac_header, skb-\u003enetwork_header, skb-\u003etransport_header and skb-\u003ecsum_start keep their old values and now describe bytes which are no longer there.  Both helpers size the new head from the old skb_end_offset(), so the stale offsets still land inside the new allocation. They point past skb_tail_pointer() though, to bytes that were never initialized.  pskb_carve_inside_nonlinear() is the worst case, because it leaves a zombie skb with an empty linear part (skb-\u003edata == skb_tail_pointer(skb), skb_headlen(skb) == 0), while skb_mac_header_was_set() is still true and skb-\u003emac_header is way ahead of skb-\u003edata.  The only user of pskb_extract() is rds_tcp_data_recv(), and the carved skb is queued on tinc-\u003eti_skb_list. When the RDS incoming message is released, rds_tcp_inc_free() calls skb_queue_purge(), which frees the skbs with SKB_DROP_REASON_QUEUE_PURGE. This is visible from drop_monitor, which then tries to pull back to the (bogus) mac header :  skbuff: __skb_pull(len=234) skb len=6968 data_len=6968 headroom=0 headlen=0 tailroom=0 end-tail=384 mac=(234,14) mac_len=14 net=(248,40) trans=288 shinfo(txflags=0 nr_frags=1 gso(size=1428 type=16 segs=5)) csum(0x100120 start=288 offset=16 ip_summed=3 complete_sw=0 valid=1 level=0) hash(0x7b446c6c sw=0 l4=1) proto=0x86dd pkttype=0 iif=60 kernel BUG at ./include/linux/skbuff.h:2847!  Add skb_carve_reset_headers() to mark the mac and transport headers as not set, reset the network header, clear skb-\u003emac_len, and drop a now meaningless CHECKSUM_PARTIAL (csum_start no longer describes anything).  Invalidate the inner offsets as well. Unlike mac_header and transport_header they have no \"unset\" sentinel, so a leftover non-zero value still looks like a real header. Zero skb-\u003einner_mac_header, skb-\u003einner_network_header, skb-\u003einner_transport_header, skb-\u003einner_protocol and skb-\u003eencapsulation, so that all the header state is invalidated in one place.  v2: fixed an inaccurate changelog. The stale offsets stay inside the     new skb-\u003ehead, which is never smaller than the old one, they     simply point past skb_tail_pointer() to bytes that are gone.     Thanks to Xuanqiang Luo for insisting on this.     Also invalidate the inner header state, as suggested by the     netdev AI review :     https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260911114922.621937-1-edumazet%40google.com",
  "id": "DEBIAN-CVE-2026-98271",
  "modified": "2026-10-07T04:47:37.669439287Z",
  "published": "2026-10-06T09:18:16.627Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-98271"
    }
  ],
  "upstream": [
    "CVE-2026-98271"
  ]
}