Answer in brief
CVE-2026-89511 records a Unknown severity vulnerability in qede: Fix NULL pointer dereference in TPA fragment processing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8a8633978b842c88fbcfe00d4e5dde96048f630e <7f911e208b3ca2c76d9f2bbba1f54b9403568c10 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <2a952fb1b20d83e83ca852773e6188511f7d2191 || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <f5c8619ccbd70102642120c4c6fda1c048a555fd || >=8a8633978b842c88fbcfe00d4e5dde96048f630e <06aa3d26327f24edd039ff249672fdf6f2ba5695 | 7f911e208b3ca2c76d9f2bbba1f54b9403568c10, 2a952fb1b20d83e83ca852773e6188511f7d2191, f5c8619ccbd70102642120c4c6fda1c048a555fd, 06aa3d26327f24edd039ff249672fdf6f2ba5695 |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.