Linux
qede: Fix NULL pointer dereference in TPA fragment processing
In the Linux kernel, the following vulnerability has been resolved: qede: Fix NULL pointer dereference in TPA fragment processing Under memory pressure, the qede driver encounters NULL pointer dereferences when processing TPA continuation fragments. Commit 8a8633978b84 ("qede: Add build_skb() support.") accidentally dropped the assignment of tpa_info->buffer.data in qede_tpa_start(). When memory pressure causes an SKB allocation failure in qede_tpa_start(), the driver sets tpa_start_fail = true and attempts to recycle the physical page later in qede_tpa_end() via qede_reuse_page(). However, because buffer.data was left uninitialized (NULL), qede_reuse_page() pushes a "ghost" BD (valid DMA mapping but NULL data pointer) back into the active Rx ring. The next time the hardware uses this ring slot, it passes a NULL page to qede_fill_frag_skb(), causing a kernel panic. Example crash from production system: BUG: unable to handle kernel NULL pointer dereference at 0x8 RIP: qede_fill_frag_skb+0x96/0x430 [qede] Call Trace: qede_rx_int+0xb06/0x1de0 qede_poll+0x2f4/0x6c0 __napi_poll+0x2d/0x130 Fix the root cause by restoring the tpa_info->buffer.data assignment in qede_tpa_start(), ensuring valid pages are correctly tracked and recycled. Additionally, update the stale comment for struct qede_agg_info::buffer to reflect its current usage.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < e2214e2793154b745436e46c6a9a7985d9b3781d
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < dd8bc0a9d87d2b048711edd17ba7286432edd285
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < fa7c9bd2c4a8de167e2fb32968ca4d91dd774375
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < a5e1fdc126ab337d601d1a00cc4b47910679d005
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < 7f911e208b3ca2c76d9f2bbba1f54b9403568c10
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < 2a952fb1b20d83e83ca852773e6188511f7d2191
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < f5c8619ccbd70102642120c4c6fda1c048a555fd
- >= 8a8633978b842c88fbcfe00d4e5dde96048f630e, < 06aa3d26327f24edd039ff249672fdf6f2ba5695
Fixed in e2214e2793154b745436e46c6a9a7985d9b3781d, dd8bc0a9d87d2b048711edd17ba7286432edd285, fa7c9bd2c4a8de167e2fb32968ca4d91dd774375, a5e1fdc126ab337d601d1a00cc4b47910679d005, 7f911e208b3ca2c76d9f2bbba1f54b9403568c10, 2a952fb1b20d83e83ca852773e6188511f7d2191, f5c8619ccbd70102642120c4c6fda1c048a555fd, 06aa3d26327f24edd039ff249672fdf6f2ba5695
- 4.18
Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to e2214e2793154b745436e46c6a9a7985d9b3781d or dd8bc0a9d87d2b048711edd17ba7286432edd285 or fa7c9bd2c4a8de167e2fb32968ca4d91dd774375 or a5e1fdc126ab337d601d1a00cc4b47910679d005 or 7f911e208b3ca2c76d9f2bbba1f54b9403568c10 or 2a952fb1b20d83e83ca852773e6188511f7d2191 or f5c8619ccbd70102642120c4c6fda1c048a555fd or 06aa3d26327f24edd039ff249672fdf6f2ba5695 or later.
Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.