CVE-2026-99081
High 7.5No known exploitationFix availablebnxt_en: fix DMA mapping length for padded small packets
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 45% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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 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) 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.
Patching and mitigation
- Patch status
- Fix available (source: Microsoft MSRC)
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- msrc.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before a51d233ccd4889aadb71dace863525cc2b00271e | a51d233ccd4889aadb71dace863525cc2b00271e | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before 2956aca14dd2977cd08bd2ccafae3beb8b84b268 | 2956aca14dd2977cd08bd2ccafae3beb8b84b268 | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before fbd977e513971ccb4f0762a7f59eac500e474f89 | fbd977e513971ccb4f0762a7f59eac500e474f89 | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before 5213f65a9667d3dd85db2e6df8f2e0516290db34 | 5213f65a9667d3dd85db2e6df8f2e0516290db34 | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before 0f347e00d060dc0bf3b2d0ee041206e54848c233 | 0f347e00d060dc0bf3b2d0ee041206e54848c233 | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before b3fd0177cf18a6ac98d41af80b4040010ea40f4d | b3fd0177cf18a6ac98d41af80b4040010ea40f4d | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before 3a5d8465e73aff3c7d1ec38261dcaaa317367467 | 3a5d8465e73aff3c7d1ec38261dcaaa317367467 | CVE Program |
| Linux | Linux | from c0c050c58d840994ba842ad1c338a98e7c12b764 before cf8530a25ae92c4493e2f22981ecb46f0b66f4c8 | cf8530a25ae92c4493e2f22981ecb46f0b66f4c8 | CVE Program |
| Linux | Linux | 4.4 | Not documented | CVE Program |
| Microsoft | azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Not documented | Not documented | Microsoft MSRC |
| Microsoft | azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Not documented | 6.6.161.1-1 | Microsoft MSRC |
| Microsoft | azl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0 | Not documented | 0:6.18.57-1.1.azl4 | Microsoft MSRC |
| Linux | Linux (unaffected) | from 5.10.273 up to and including 5.10.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 5.15.224 up to and including 5.15.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.1.191 up to and including 6.1.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.113 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.57 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.6.160 up to and including 6.6.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.2.11 up to and including 7.2.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.3 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 4.4 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Advisory
Microsoft advisory published
Advisory change
Microsoft advisory revised (2.0): Information published.
Advisory change
Microsoft advisory revised (3.0): Information published.
Advisory change
Microsoft advisory revised (4.0): Information published.
Advisory change
Microsoft advisory revised (5.0): Information published.
Advisory change
Microsoft advisory revised (6.0): Information published.
Advisory change
Microsoft advisory revised (7.0): Information published.
Patch
Fix documented by Microsoft MSRC
Vendor guidance and references
- Microsoft Security Update Guide (opens in a new tab)vendor-advisory
- https://git.kernel.org/stable/c/0f347e00d060dc0bf3b2d0ee041206e54848c233 (opens in a new tab)
- https://git.kernel.org/stable/c/2956aca14dd2977cd08bd2ccafae3beb8b84b268 (opens in a new tab)
- https://git.kernel.org/stable/c/3a5d8465e73aff3c7d1ec38261dcaaa317367467 (opens in a new tab)
- https://git.kernel.org/stable/c/5213f65a9667d3dd85db2e6df8f2e0516290db34 (opens in a new tab)
- https://git.kernel.org/stable/c/a51d233ccd4889aadb71dace863525cc2b00271e (opens in a new tab)
- https://git.kernel.org/stable/c/b3fd0177cf18a6ac98d41af80b4040010ea40f4d (opens in a new tab)
- https://git.kernel.org/stable/c/cf8530a25ae92c4493e2f22981ecb46f0b66f4c8 (opens in a new tab)
- https://git.kernel.org/stable/c/fbd977e513971ccb4f0762a7f59eac500e474f89 (opens in a new tab)