Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-89511

qede: Fix NULL pointer dereference in TPA fragment processing

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in e2214e2793154b745436e46c6a9a7985d9b3781d; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in dd8bc0a9d87d2b048711edd17ba7286432edd285; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in fa7c9bd2c4a8de167e2fb32968ca4d91dd774375; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in a5e1fdc126ab337d601d1a00cc4b47910679d005; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in 7f911e208b3ca2c76d9f2bbba1f54b9403568c10; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in 2a952fb1b20d83e83ca852773e6188511f7d2191; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in f5c8619ccbd70102642120c4c6fda1c048a555fd; From 8a8633978b842c88fbcfe00d4e5dde96048f630e · fixed in 06aa3d26327f24edd039ff249672fdf6f2ba5695

  • Linux Linux

    4.18

  • KernelLinux

    From 4.18.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4

References 8

git.kernel.org