CVE-2026-89511

CVE CVE-2026-89511EUVD EUVD-2026-76417Published 2026-09-11T19:43:56.000ZLast changed 2026-09-14T12:00:37.000ZCVSS 7.5

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.3-rc1; patch: 7.2.4; 8a8633978b842c88fbcfe00d4e5dde96048f630e <e2214e2793154b745436e46c6a9a7985d9b3781d; patch: 6.12.109; patch: 0; 8a8633978b842c88fbcfe00d4e5dde96048f630e <06aa3d26327f24edd039ff249672fdf6f2ba5695; 8a8633978b842c88fbcfe00d4e5dde96048f630e <a5e1fdc126ab337d601d1a00cc4b47910679d005; 8a8633978b842c88fbcfe00d4e5dde96048f630e <7f911e208b3ca2c76d9f2bbba1f54b9403568c10; patch: 5.15.221; patch: 6.1.188; patch: 5.10.270; 4.18; 8a8633978b842c88fbcfe00d4e5dde96048f630e <fa7c9bd2c4a8de167e2fb32968ca4d91dd774375; patch: 6.6.157; 8a8633978b842c88fbcfe00d4e5dde96048f630e <f5c8619ccbd70102642120c4c6fda1c048a555fd; 8a8633978b842c88fbcfe00d4e5dde96048f630e <dd8bc0a9d87d2b048711edd17ba7286432edd285; patch: 6.18.50; 8a8633978b842c88fbcfe00d4e5dde96048f630e <2a952fb1b20d83e83ca852773e6188511f7d2191

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.