Page MenuHomeFreeBSD

Don't send TCP segments when the IP header chain and the TCP header doesn't fit in a packet
ClosedPublic

Authored by tuexen on Sep 15 2019, 3:36 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Jan 23, 5:51 AM
Unknown Object (File)
Thu, Jan 9, 12:40 AM
Unknown Object (File)
Dec 7 2024, 7:11 PM
Unknown Object (File)
Dec 2 2024, 3:35 AM
Unknown Object (File)
Nov 29 2024, 2:28 PM
Unknown Object (File)
Nov 24 2024, 10:55 PM
Unknown Object (File)
Nov 24 2024, 8:59 PM
Unknown Object (File)
Nov 24 2024, 7:17 AM
Subscribers

Details

Summary

RFC 7112 requires a host to put the complete IP header chain including the TCP header in the first IP packet. Enforce this in tcp_output(). Without this check, a kernel with INVARIANTS will panic.

This issue was found by running an instance of syzkaller.

Test Plan

Test with the reproducer generated by syzkaller:


Here is the issue: panic: {tcp_output:LINE}: len < 0.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

sys/netinet/tcp_output.c
944 ↗(On Diff #62126)

From transport-call: make this a >= to have at least 1 data byte per segment, to make forward progress. Otherwise, we may continously send packet with just ip+tcp headers forever.

Allow at least one byte of payload to ensure that making progress is possible. This was suggested in the transport telco.

sys/netinet/tcp_output.c
944 ↗(On Diff #62126)

Addressed by the last change. The same change is also applied to RACK and BBR.

This revision was not accepted when it landed; it landed in state Needs Review.Sep 29 2019, 10:45 AM
This revision was automatically updated to reflect the committed changes.