{
  "id": "CVE-2026-99081",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-99081",
  "published_at": "2026-10-23T12:23:28.347Z",
  "title": "bnxt_en: fix DMA mapping length for padded small packets",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.5,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: fix DMA mapping length for padded small packets\n\nStefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412\nNetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:\n\n  DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000\n        [fault reason 0x06] PTE Read access is not set\n  bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001\n  ...\n  NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out\n\nThe fault address (0xfc499000) is on an exact 4KB page boundary,\npointing to a DMA read buffer overrun.\n\nIn bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes),\nsuch as 42-byte untagged ARP frames, are padded:\n\n    if (length \u003c BNXT_MIN_PKT_SIZE) {\n        pad = BNXT_MIN_PKT_SIZE - length;\n        if (skb_pad(skb, pad))\n            goto tx_kick_pending;\n        length = BNXT_MIN_PKT_SIZE;\n    }\n\n    mapping = dma_map_single(\u0026pdev-\u003edev, skb-\u003edata, len, DMA_TO_DEVICE);\n    ...\n    dma_unmap_len_set(tx_buf, len, len);\n\nHowever, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes)\nand is left unadjusted after padding. Consequently, dma_map_single() and\ndma_unmap_len_set() map and track only 42 bytes.\n\nLater, the hardware TX buffer descriptor is programmed with the padded length:\n\n    txbd-\u003etx_bd_len_flags_type =\n        cpu_to_le32(((len + pad) \u003c\u003c TX_BD_LEN_SHIFT) | flags |\n                    TX_BD_FLAGS_PACKET_END);\n\nThe NIC DMA engine is thus instructed to read 52 bytes from a region where\nonly 42 bytes were DMA-mapped. If skb-\u003edata ends near the boundary of a 4KB\npage (within 'pad' bytes of the next page), the hardware DMA read overruns\ninto the unmapped adjacent page, triggering an IOMMU fault.\n\nThis issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic\nand races when toggling HW VLAN offload\") because reserving extra VLAN\nheadroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb-\u003edata\noffsets and potentially causing small frames to land right against page\nboundaries.\n\nFix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in\nbnxt_start_xmit(), before skb_shinfo(skb)-\u003enr_frags is sampled,\nbecause padding might linearize the skb.\nThis ensures skb-\u003elen and skb_headlen(skb) reflect the padded size so\nthat dma_map_single() maps the full buffer and the descriptor length is\nconsistent. This also removes the temporary 'pad' variable and masking logic.\n\nThe padding is done after the SW USO branch, otherwise\nbnxt_sw_udp_gso_xmit() would account the padding as UDP payload\nand send it in extra segments.\n\nNote that SW USO segments are still not padded: with IPv4, a segment\ncarrying less than 10 bytes of UDP payload (small gso_size, or a short\nlast segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE.\nThis is a separate issue, left for a followup patch.",
  "cvss_by_source": {
    "cna": 7.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c 0f347e00d060dc0bf3b2d0ee041206e54848c233",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c b3fd0177cf18a6ac98d41af80b4040010ea40f4d",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c 3a5d8465e73aff3c7d1ec38261dcaaa317367467",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c cf8530a25ae92c4493e2f22981ecb46f0b66f4c8",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c 2956aca14dd2977cd08bd2ccafae3beb8b84b268",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c fbd977e513971ccb4f0762a7f59eac500e474f89",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c 5213f65a9667d3dd85db2e6df8f2e0516290db34",
          "\u003e= c0c050c58d840994ba842ad1c338a98e7c12b764, \u003c a51d233ccd4889aadb71dace863525cc2b00271e"
        ],
        "fixed_in": [
          "0f347e00d060dc0bf3b2d0ee041206e54848c233",
          "b3fd0177cf18a6ac98d41af80b4040010ea40f4d",
          "3a5d8465e73aff3c7d1ec38261dcaaa317367467",
          "cf8530a25ae92c4493e2f22981ecb46f0b66f4c8",
          "2956aca14dd2977cd08bd2ccafae3beb8b84b268",
          "fbd977e513971ccb4f0762a7f59eac500e474f89",
          "5213f65a9667d3dd85db2e6df8f2e0516290db34",
          "a51d233ccd4889aadb71dace863525cc2b00271e"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "4.4"
        ],
        "fixed_in": [
          "0",
          "5.10.273",
          "5.15.224",
          "6.1.191",
          "6.6.160",
          "6.12.113",
          "6.18.57",
          "7.2.11",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 0f347e00d060dc0bf3b2d0ee041206e54848c233 or b3fd0177cf18a6ac98d41af80b4040010ea40f4d or 3a5d8465e73aff3c7d1ec38261dcaaa317367467 or cf8530a25ae92c4493e2f22981ecb46f0b66f4c8 or 2956aca14dd2977cd08bd2ccafae3beb8b84b268 or fbd977e513971ccb4f0762a7f59eac500e474f89 or 5213f65a9667d3dd85db2e6df8f2e0516290db34 or a51d233ccd4889aadb71dace863525cc2b00271e or later.",
      "Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.160 or 6.12.113 or 6.18.57 or 7.2.11 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
