CVE-2026-74269bnxt: fix head underflow on XDP head-grow
- 9.8CriticalCVSS base score
- 0.49%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.49% · top 57% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16 – < 59f6211c006cb5936b443fb396eb43864ca21ed5
- affected f6974b4c2d8e1062b5a52228ee47293c15b4ee1e – < 3e8f3959a7fd28461b8cd9708c21286b4250b77a
- affected f6974b4c2d8e1062b5a52228ee47293c15b4ee1e – < ff34e5a26a26c92142afea11455e259c4c4c617b
- affected f6974b4c2d8e1062b5a52228ee47293c15b4ee1e – < 4c03275bc4435cc8e25f7f3f08aff58c0e783d8d
- affected f6974b4c2d8e1062b5a52228ee47293c15b4ee1e – < bb72b1c6755631c74b7e0878ee55bb81c06776c0
- affected f6974b4c2d8e1062b5a52228ee47293c15b4ee1e – < e26657fe3b85c068b01f42bb0c602f242d643ba9
- affected ae0e135dc900827687ecc684c2bbb57aae48d318
- affected 6.1.45 – < 6.1.191
- affected 6.4.10 – < 6.5
- affected 6.5
- unaffected < 6.5
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/59f6211c006cb5936b443fb396eb43864ca21ed5 (opens in a new tab)
- https://git.kernel.org/stable/c/3e8f3959a7fd28461b8cd9708c21286b4250b77a (opens in a new tab)
- https://git.kernel.org/stable/c/ff34e5a26a26c92142afea11455e259c4c4c617b (opens in a new tab)
- https://git.kernel.org/stable/c/4c03275bc4435cc8e25f7f3f08aff58c0e783d8d (opens in a new tab)
- https://git.kernel.org/stable/c/bb72b1c6755631c74b7e0878ee55bb81c06776c0 (opens in a new tab)
- https://git.kernel.org/stable/c/e26657fe3b85c068b01f42bb0c602f242d643ba9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59416 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74269)Record last updated .