CVE-2026-99081

bnxt_en: fix DMA mapping length for padded small packets

  • High 7.5

Description

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix DMA mapping length for padded small packets Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces: DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000 [fault reason 0x06] PTE Read access is not set bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001 ... NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun. In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded: if (length < BNXT_MIN_PKT_SIZE) { pad = BNXT_MIN_PKT_SIZE - length; if (skb_pad(skb, pad)) goto tx_kick_pending; length = BNXT_MIN_PKT_SIZE; } mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE); ... dma_unmap_len_set(tx_buf, len, len); However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes. Later, the hardware TX buffer descriptor is programmed with the padded length: txbd->tx_bd_len_flags_type = cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags | TX_BD_FLAGS_PACKET_END); The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault. This issue was exposed after commit 447cbe95ebb9 ("vlan: fix skb_under_panic and races when toggling HW VLAN offload") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries. Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic. The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments. Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.

Key facts

Published
23 Oct 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.518% likely to be exploited in the next 30 days, higher than 44.648% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding 0f347e00d060dc0bf3b2d0ee041206e54848c233 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding b3fd0177cf18a6ac98d41af80b4040010ea40f4d (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding 3a5d8465e73aff3c7d1ec38261dcaaa317367467 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding cf8530a25ae92c4493e2f22981ecb46f0b66f4c8 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding 2956aca14dd2977cd08bd2ccafae3beb8b84b268 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding fbd977e513971ccb4f0762a7f59eac500e474f89 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding 5213f65a9667d3dd85db2e6df8f2e0516290db34 (affected)
  • c0c050c58d840994ba842ad1c338a98e7c12b764 up to but excluding a51d233ccd4889aadb71dace863525cc2b00271e (affected)
LinuxLinux
  • Default status: affected
  • 4.4 (affected)
  • 0 up to but excluding 4.4 (unaffected)
  • 5.10.273 up to and including 5.10.* (unaffected)
  • 5.15.224 up to and including 5.15.* (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References