bnxt: fix head underflow on XDP head-grow
CVE-2026-74269 is fixed in 16 products on 1 platform, first by DEBIAN-CVE-2026-74269, released August 15, 2026. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.38.1.160000.2.22 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.81.1.150700.17.45.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.38.1.160000.2.23 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-livepatch-SLE15-SP7-RT_Update_20 · sles 15.7 | 1-150700.1.3.1 | SUSE-SU-2026:4120-1 | Sep 10, 2026 |
| kernel-livepatch-SLE15-SP7_Update_21 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.38.1 | OPENSUSE-SU-2026:21910-1 | Sep 22, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.81.1 | SUSE-SU-2026:4254-1 | Oct 7, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.38.1 | SUSE-SU-2026:23902-1 | Sep 22, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.115-2 | DEBIAN-CVE-2026-74269 | Aug 15, 2026 |
| linux · Debian 14 | 7.1.5-1 | DEBIAN-CVE-2026-74269 | Aug 15, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.