PT-2026-152516
CVE-2026-99636
·
Published
2026-11-20
·
Updated
2026-11-20
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
net: reject a negative TCP header offset in qdisc pkt len segs init()
qdisc pkt len segs init() stores skb transport offset(), or the inner
offset, in the unsigned hdr len. A header in front of skb->data gives a
negative offset. For an offset a little below zero, pskb may pull() gets a
small length and succeeds. Then a 64-bit kernel reads the TCP header far
after the skb and can crash. Further below zero pskb may pull() fails.
Commit 28a57fb2c5df ("net: iptunnel: fix stale transport header during
tunnel decapsulation") fixed one source of such offsets. Other code that
removes bytes from the front of a packet can leave the same stale header.
Return SKB DROP REASON SKB BAD GSO for a negative offset in the TCP branch.
SKB GSO UDP L4 and the other GSO types read no header and still get a wrong
qdisc pkt len(). On a 64-bit kernel only packets that cause the read after
the skb today get a new result. Then dev queue xmit() drops them and
returns -EINVAL, but sch handle ingress() ignores the result. Their content
can be valid. Thus the code that leaves the header stale needs its own fix.
Found an issue in the description? Have something to add? Feel free to write us 👾