From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154443; b=hmjhSt1Lc/IrredJALDpm5L2ZQ8dz7UglAa5UbmXkh3EQnrhCvsul7zi6gghceohAHD4 +2JS3jfCFHdzk9Yebc/Eb59YGOHeAZbWjCEe/w1z5mzgi1WbcAgCc2qsHcdGBW0VqVwFR Qh3CrM3YX+F+MAK0e91+0w36sx3zVDpvFCO2qeJZCMLq3VI1q2s9yNGCGhmdg56jXMsI9 SRNPOIKQpB9szy+WD5izV//uCx7/xCqN/fkHpmHtig45dSy8I197NcW0HFX2OMpTIlril 4p0b95rOyeJtVjDaDM/YrapR1YewumKLIzTZEU3cY1OEowUgJ16zA9p0kx1cf97tv4g== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154443; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=UJGrsaqsffmBpfTbQvdd/4AQdh7fPYayvhWu99bML1s=; b=j3kzeGnfLyKoH+/oZNTrXxHe9OYi+WcwQFWDFsaPelvp7iMc4PWzUUFDnWa0yOcb/28h TttozN7qc/OzmnpvuxXV/SGcKkJMLukN/c4Fabbwm6k/ou1GY4uVMN04FySLs7RYYp3/2 5sk3zWaJ5IbWbGxHdWTT9nkopEYd9/fPjwJZ43QUtD76n8WPkIixz33vcEJ3ynsvijPXV X5Yje183n0wJaboqsgxNr+oPNaUkoerFv5eOrh6H5XbpYBOYudUF1AkgX8WylJMIYsk39 HMIQYfB5nqdtV859cdYwwyAI1zka3Sao5wo4J0v1u/BZoeL9pH5kt06PbLoAjrh/t9Q== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=1PEPeFoP; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2DCA4606A51F for ; Fri, 20 Nov 2026 06:00:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=1PEPeFoP Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7E2681F000CA; Fri, 20 Nov 2026 06:00:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154443; bh=UJGrsaqsffmBpfTbQvdd/4AQdh7fPYayvhWu99bML1s=; h=From:To:Cc:Subject:Date:Reply-To; b=1PEPeFoPFlBgLfUPsPMfM/RROJLmJH8hW0hDamAjaz1Ee7n4pEBf4B5C5N679ndIS /QP+9XXefNmqP0WIaHSM6qeTYxFQlyah5YcPJRowA7O0XTsmh9Zq+4PqFHiX3l+Y+C 0axJFISoVGgvXyOcMZJXhspvPeCC62PrXrEI6sLM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99744: net: atl1c: drop oversized RX frames instead of panicking Date: Fri, 20 Nov 2026 06:52:10 +0100 Message-ID: <2026112018-CVE-2026-99744-deb7@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4221; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=4ZJBS8Lq+FEU3XnMrNomGWNAJdYYRoy382r7yQzGfgY=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78/6wfnHoKpqPl/oqpSDXft9ZGb9FlI0XWFSe/jFG eOn4j5fO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi9/sYFlwLNnW8te+yxeYd n+dfUDo7bzPL5I8M893+P2U8naUsLCTT/Pfo4gYvnZ2CQQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: net: atl1c: drop oversized RX frames instead of panicking atl1c sizes its receive buffers from the netdev MTU plus a fixed set of L2 overheads, which comes to 1522 bytes at the default MTU. A link partner that sends a longer frame - in practice a MikroTik CCR2004-1G-2XS-PCIe, whose RouterOS side defaults to l2mtu 1600 while the host stays at MTU 1500 - makes the length reported by the RX return descriptor exceed what the hardware wrote, and skb_put() then either includes bytes that were never received or trips skb_over_panic and takes the host down. Compare the descriptor length against buffer_info->length, the length the hardware was given, rather than against skb_tailroom(): the skb carries 64 bytes of slack for the DMA erratum, so tailroom is larger than the DMA buffer and a frame in between would pass the check and still be delivered with a tail the device never wrote. The same test rejects frames shorter than ETH_HLEN + ETH_FCS_LEN; before this change a reported length below ETH_FCS_LEN underflowed in skb_put(). The frame is dropped with kfree_skb_reason(SKB_DROP_REASON_PKT_TOO_BIG) so drop_monitor and the kfree_skb tracepoint see it, and counted through dev_core_stats_rx_dropped_inc(), which survives atl1c_get_stats() overwriting the hardware counters on every read. It also counts as work: atl1c_clean_rfd() has already recycled the RFD, and the refill at the end of the poll only runs when work_done is non-zero, so sustained oversized traffic would otherwise drain the ring and stop RX. Tested on a MikroTik CCR2004-1G-2XS-PCIe (4x AR8151) in a Proxmox VE host, with atl1c built from a DKMS tree carrying this change: the l2mtu-1600 traffic that panics the stock driver is dropped and counted with the patch applied, and received normally once the host MTU is raised to match. This complements commit 36c2009d90f2 ("net: atl1c: fix soft lockup on out-of-range tpd_cons read"), which fixed the TX side of the same "host dies while the card resets" problem. The Linux kernel CVE team has assigned CVE-2026-99744 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.29 with commit 43250ddd75a35d1f7926d989a10fefd30c37eaa7 and fixed in 6.12.118 with commit 11c873d6e6a497b5ee3699c63b57b49a882aa580 Issue introduced in 2.6.29 with commit 43250ddd75a35d1f7926d989a10fefd30c37eaa7 and fixed in 6.18.64 with commit 655463ba1de62e7f4893cabfc89fe70d0e33f55d Issue introduced in 2.6.29 with commit 43250ddd75a35d1f7926d989a10fefd30c37eaa7 and fixed in 7.3.5 with commit 18ca06b36c4da8b46859dcd1c9aec557d05bc23a Issue introduced in 2.6.29 with commit 43250ddd75a35d1f7926d989a10fefd30c37eaa7 and fixed in 7.4-rc2 with commit c4ba1716853de5178a9df785844ebb5e397a80e6 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-99744 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/ethernet/atheros/atl1c/atl1c_main.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/11c873d6e6a497b5ee3699c63b57b49a882aa580 https://git.kernel.org/stable/c/655463ba1de62e7f4893cabfc89fe70d0e33f55d https://git.kernel.org/stable/c/18ca06b36c4da8b46859dcd1c9aec557d05bc23a https://git.kernel.org/stable/c/c4ba1716853de5178a9df785844ebb5e397a80e6