CVE-2026-99744: Proxmox VE: 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
This Proxmox advisory covers CVE-2026-99744. Related products: Proxmox VE, Proxmox.
- CVE-2026-99744
Key facts
- CISA KEV
- Not listed (catalogue checked )
- Source published
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
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:
Text from the source record.
How to fix CVE-2026-99744
Vendor guidance
- 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.
End-of-life dates for Proxmox VE
More Proxmox advisories
CVE-2026-51082Jul 17, 2026race condition between the vncproxy and vncwebsocket API calls in Proxmox VirtualCVE-2026-25199May 8, 2026Instances deployed via the Proxmox extensionCVE-2022-28144Mar 29, 2022Jenkins Proxmox Plugin 0.7.0 and earlier does not perform a permission check in severalCVE-2022-28143Mar 29, 2022cross-site request forgery (CSRF) vulnerability in Jenkins Proxmox Plugin 0.7.0PSA-2026-00100Nov 12, 2026Proxmox Virtual Environment: Missing shell quoting in upload error handlingPSA-2026-00099Nov 10, 2026Proxmox: Incomplete validation of UPID when handling "stop task" API requests
Get an email when Proxmox Virtual Environment (VE) publishes the next one.
See Proxmox Virtual Environment (VE)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.