Bug 2541078 (CVE-2026-97574) - CVE-2026-97574 kernel: bnxt_en: Don't free the live ring's TPA state on queue restart failure
Summary: CVE-2026-97574 kernel: bnxt_en: Don't free the live ring's TPA state on queue...
Keywords:
Status: NEW
Alias: CVE-2026-97574
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 10:46 UTC by OSIDB Bzimport
Modified: 2026-09-29 05:11 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 10:46:11 UTC
In the Linux kernel, the following vulnerability has been resolved:

bnxt_en: Don't free the live ring's TPA state on queue restart failure

bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:

  memcpy(clone, rxr, sizeof(*rxr));

the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.

If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring's memory can be freed while still in use.

Fix this by initializing the clone's pointers to NULL to prevent live
ring state from being freed inadvertently.


Note You need to log in before you can comment on or make changes to this bug.