net OFOQueue Exhaustion

Vulnerability analysis

The original TCP input processing repeatedly scanned and copied large numbers of tiny, completely out-of-order queued packets even though this work did not reduce memory consumption, allowing incoming packet volume to cause disproportionate processing cost. The fix stops attempting to coalesce tiny segments and abandons a pathological range once its accumulated size becomes excessive, allowing the less expensive queue-pruning behavior to handle it. A remote TCP peer with network access to an affected endpoint can trigger the condition without authentication or local privileges, causing major availability impact; no special hardware or nondefault configuration is indicated.