Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89511qede: Fix NULL pointer dereference in TPA fragment processing

Description

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. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89511, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.71% · top 46% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < e2214e2793154b745436e46c6a9a7985d9b3781d
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < dd8bc0a9d87d2b048711edd17ba7286432edd285
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < fa7c9bd2c4a8de167e2fb32968ca4d91dd774375
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < a5e1fdc126ab337d601d1a00cc4b47910679d005
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < 7f911e208b3ca2c76d9f2bbba1f54b9403568c10
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < 2a952fb1b20d83e83ca852773e6188511f7d2191
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < f5c8619ccbd70102642120c4c6fda1c048a555fd
    • affected 8a8633978b842c88fbcfe00d4e5dde96048f630e – < 06aa3d26327f24edd039ff249672fdf6f2ba5695
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89511 badge
[![CVE-2026-89511](https://cveledger.app/badge/CVE-2026-89511.svg)](https://cveledger.app/cve/CVE-2026-89511)

Record last updated .