CVE-2026-99744: net: atl1c: drop oversized RX frames instead of panicking

Published Nov 20, 2026
·
Updated

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 skbput() then either includes bytes that were never received or trips skboverpanic and takes the host down.

Compare the descriptor length against bufferinfo->length, the length the hardware was given, rather than against skbtailroom(): 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 ETHHLEN + ETHFCSLEN; before this change a reported length below ETHFCSLEN underflowed in skbput().

The frame is dropped with kfreeskbreason(SKBDROPREASONPKTTOOBIG) so dropmonitor and the kfreeskb tracepoint see it, and counted through devcorestatsrxdroppedinc(), which survives atl1cgetstats() overwriting the hardware counters on every read. It also counts as work: atl1ccleanrfd() has already recycled the RFD, and the refill at the end of the poll only runs when workdone 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 tpdcons read"), which fixed the TX side of the same "host dies while the card resets" problem.

Affected Software

7 affected componentsFixes available
linux/kernel>=2.6.29<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  5. Configuration

    Raise the host MTU to match the link partner's l2mtu of 1600.

    atl1c network interface MTU = 1600

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux atl1c network driver are exposed when the NIC receives a frame whose reported length exceeds the DMA receive buffer length. A documented trigger is a host using the default 1500-byte MTU connected to a peer with an L2 MTU of 1600.

2

What must an attacker or problematic peer be able to do?

They must be able to send oversized or invalid-length Ethernet frames through the affected network interface. The issue arises at the link-partner level; the provided data does not indicate exploitation from a non-adjacent network path.

3

Are default settings sufficient to avoid the problem?

No. The atl1c receive buffer is 1522 bytes with the default MTU, and a peer configured with a larger L2 MTU can send frames that exceed it even while the host remains at MTU 1500.

4

What can be done before the fix is available?

Ensure connected peers do not transmit frames larger than the host interface can receive. In particular, avoid L2 MTU mismatches such as a peer using l2mtu 1600 while the atl1c host uses the default MTU configuration.

5

What symptoms indicate possible exposure?

An affected host can panic through skb_over_panic and go down after receiving an oversized frame. Invalid short reported lengths can also cause an skb_put() underflow condition.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203