Bug 2536483 (CVE-2026-90417) - CVE-2026-90417 kernel: RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry()
Summary: CVE-2026-90417 kernel: RDMA/cxgb4: Fix dereg_skb leak and double free in writ...
Keywords:
Status: NEW
Alias: CVE-2026-90417
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 18:10 UTC by OSIDB Bzimport
Modified: 2026-10-20 12:00 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 18:10:19 UTC
In the Linux kernel, the following vulnerability has been resolved:

RDMA/cxgb4: Fix dereg_skb leak and double free in write_tpt_entry()

When the device is in the fatal error state, write_tpt_entry() returns -EIO
before handing the caller's preallocated skb to the transmit path; its
allocation-failure returns do the same. c4iw_dereg_mr() ignores the error
and frees mhp, leaking mhp->dereg_skb. c4iw_get_dma_mr() instead frees the
skb a second time after dereg_mem() already consumed it, a double free.

Make write_tpt_entry() the sole owner of a non-NULL skb, freeing it on
every return preceding handoff to c4iw_ofld_send(): fatal error, tpt and
stag allocation failure. c4iw_ofld_send() consumes the skb on success and
error alike, so drop the redundant kfree_skb() in c4iw_get_dma_mr() after
dereg_mem().


Note You need to log in before you can comment on or make changes to this bug.