{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-89511", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-89511" ], "published": "2026-09-11T19:47:07Z", "summary": "qede: Fix NULL pointer dereference in TPA fragment processing", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nqede: Fix NULL pointer dereference in TPA fragment processing\n\nUnder memory pressure, the qede driver encounters NULL pointer\ndereferences when processing TPA continuation fragments.\n\nCommit 8a8633978b84 (\"qede: Add build_skb() support.\") accidentally\ndropped the assignment of tpa_info->buffer.data in qede_tpa_start().\n\nWhen memory pressure causes an SKB allocation failure in qede_tpa_start(),\nthe driver sets tpa_start_fail = true and attempts to recycle the physical\npage later in qede_tpa_end() via qede_reuse_page(). However, because\nbuffer.data was left uninitialized (NULL), qede_reuse_page() pushes a\n\"ghost\" BD (valid DMA mapping but NULL data pointer) back into the\nactive Rx ring.\n\nThe next time the hardware uses this ring slot, it passes a NULL page\nto qede_fill_frag_skb(), causing a kernel panic.\n\nExample crash from production system:\n BUG: unable to handle kernel NULL pointer dereference at 0x8\n RIP: qede_fill_frag_skb+0x96/0x430 [qede]\n Call Trace:\n qede_rx_int+0xb06/0x1de0\n qede_poll+0x2f4/0x6c0\n __napi_poll+0x2d/0x130\n\nFix the root cause by restoring the tpa_info->buffer.data assignment\nin qede_tpa_start(), ensuring valid pages are correctly tracked and\nrecycled. Additionally, update the stale comment for\nstruct qede_agg_info::buffer to reflect its current usage.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.47-1+rpt4" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" } ] }, "database_specific": { "per_version": { "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.188", "compiled_filter": false } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-89511" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/e2214e2793154b745436e46c6a9a7985d9b3781d" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/dd8bc0a9d87d2b048711edd17ba7286432edd285" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/fa7c9bd2c4a8de167e2fb32968ca4d91dd774375" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/a5e1fdc126ab337d601d1a00cc4b47910679d005" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/7f911e208b3ca2c76d9f2bbba1f54b9403568c10" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/2a952fb1b20d83e83ca852773e6188511f7d2191" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/f5c8619ccbd70102642120c4c6fda1c048a555fd" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/06aa3d26327f24edd039ff249672fdf6f2ba5695" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-09-14T12:06:03Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.5, "cvss_v3_severity": "High", "scenario": "AV:N - The bug is in qede TPA/GRO RX on Marvell/QLogic FastLinQ NICs used on internet-facing datacenter and cloud servers. Remote TCP segments cause firmware to post TPA CQEs handled by qede_msix_fp_int()->qede_poll()->qede_rx_int()->qede_rx_process_tpa_cqe()->qede_tpa_start()/qede_tpa_end()/qede_fill_frag_skb().\nAC:L - An attacker can send high-rate TCP streams that HW GRO (enabled by default) aggregates and flood GFP_ATOMIC skb allocations until qede_tpa_start() fails, then keep sending so the recycled ghost BD is consumed. No uncontrolled race or victim-specific layout is required; the attacker drives TPA and the allocation-failure condition.\nPR:N - NIC receive and TPA completion handling run in softirq on inbound frames with no authentication, capability check, or local account. Any unauthenticated remote host that can send Ethernet/TCP traffic to a qede interface can reach the vulnerable path.\nUI:N - Packet reception, MSI-X interrupt handling, and NAPI polling process attacker frames automatically whenever the qede interface is up. The victim need not mount a filesystem, open a device, or otherwise interact.\nS:U - The NULL dereference oops stays in the host kernel that owns the qede driver and RX rings. It does not cross a VM, IOMMU, container, or other security-authority boundary.\nC:N - The fault is a pure NULL page-pointer dereference in qede_fill_frag_skb() (production RIP at offset 0x8) when a recycled ghost BD with buffer.data==NULL is consumed. There is no use-after-free reclaim, out-of-bounds read, or other disclosure primitive.\nI:N - skb_fill_page_desc()/page_ref_inc() abort immediately on the NULL page pointer without writing attacker-controlled data into other kernel objects, so there is no arbitrary-write or control-flow hijack primitive.\nA:H - The documented production crash is a kernel NULL pointer dereference panic in NAPI/softirq context (qede_fill_frag_skb), which is a complete availability impact under kernel CVSS guidance and can be retriggered by further traffic." } } }