This is a regression vulnerability in the bnxt driver where a fix for large page support introduced a double-free that only manifests on driver teardown, making it exceptionally difficult to diagnose in production. The original large-page fix added a fixed rx_offset subtraction (258 bytes) to handle NET_IP_ALIGN + XDP_PACKET_HEADROOM, but this arithmetic fails when XDP head-adjustment operations shift data_ptr to within 2 bytes of the fragment start—creating a head-underflow that drops the page pool fragment reference on the wrong page. Normal packet processing continues unaffected because the corrupted reference count only matters when the prematurely recycled page is encountered again, which typically happens only at driver teardown. This latency is the critical diagnostic challenge: the developer who wrote the regression fix ran tests that passed because they validated the large-page scenario in isolation, not the interaction between XDP head-grow and the new offset subtraction. The fix—adding an offset field to bnxt_sw_rx_bd—is structurally correct, but the deeper concern is blast radius through the shared page pool infrastructure. When the corrupted page re-enters the free list, it can be handed out to any driver using that pool, creating a lateral corruption vector that affects the entire system rather than just bnxt. Between the incorrect free and driver teardown, there's a latent use-after-free window that standard page pool safeguards cannot detect because they trust the reference count. This isn't just a crash-on-shutdown bug—it silently corrupts memory state that can propagate across driver boundaries. The 258-byte constant itself is a frozen snapshot of architectural assumptions (NET_IP_ALIGN + XDP_PACKET_HEADROOM) that were never re-audited across all supported architectures and page sizes. The priority question is whether other bnxt receive paths have similar fixed-offset assumptions, and whether other kernel drivers with analogous rx_offset subtraction patterns should be audited for this same head-grow interaction. For defenders: prioritize this patch in containerized environments where driver teardown occurs during namespace cleanup, and monitor for unexplained reference count warnings in page pool allocations preceding any bnxt unload events.
CVE-2026-74269
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $5,750. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-74269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis is a regression vulnerability in the bnxt driver where a fix for large page support introduced a double-free that only manifests on driver teardown, making it exceptionally difficult to diagnose in production. The original large-page fix added a fixed rx_offset subtraction (258 bytes) to handle NET_IP_ALIGN + XDP_PACKET_HEADROOM, but this arithmetic fails when XDP head-adjustment operations shift data_ptr to within 2 bytes of the fragment start—creating a head-underflow that drops the page pool fragment reference on the wrong page. Normal packet processing continues unaffected because the corrupted reference count only matters when the prematurely recycled page is encountered again, which typically happens only at driver teardown. This latency is the critical diagnostic challenge: the developer who wrote the regression fix ran tests that passed because they validated the large-page scenario in isolation, not the interaction between XDP head-grow and the new offset subtraction. The fix—adding an offset field to bnxt_sw_rx_bd—is structurally correct, but the deeper concern is blast radius through the shared page pool infrastructure. When the corrupted page re-enters the free list, it can be handed out to any driver using that pool, creating a lateral corruption vector that affects the entire system rather than just bnxt. Between the incorrect free and driver teardown, there's a latent use-after-free window that standard page pool safeguards cannot detect because they trust the reference count. This isn't just a crash-on-shutdown bug—it silently corrupts memory state that can propagate across driver boundaries. The 258-byte constant itself is a frozen snapshot of architectural assumptions (NET_IP_ALIGN + XDP_PACKET_HEADROOM) that were never re-audited across all supported architectures and page sizes. The priority question is whether other bnxt receive paths have similar fixed-offset assumptions, and whether other kernel drivers with analogous rx_offset subtraction patterns should be audited for this same head-grow interaction. For defenders: prioritize this patch in containerized environments where driver teardown occurs during namespace cleanup, and monitor for unexplained reference count warnings in page pool allocations preceding any bnxt unload events.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-74269 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data