CVE-2026-90219

RDMA/cxgb4: Free debugfs on registration failure

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/cxgb4: Free debugfs on registration failure c4iw_alloc() creates the per-device debugfs tree (dev->debugfs_root via setup_debugfs()), but it is removed only in c4iw_remove(), not in c4iw_dealloc(). When RDMA device registration fails, the registration worker's err_dealloc_ctx path calls c4iw_dealloc() directly, bypassing c4iw_remove(), so the debugfs dentries leak and outlive the freed c4iw_dev. Move debugfs_remove_recursive() into c4iw_dealloc() so every path that frees ctx->dev also removes its debugfs tree.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.13049ea0c036ede81f126f1a9389d377999fdf5c5a15.4.495.7.65.898fa991017981b52dcc4dc3924fc8e1e83e41bf49c0cec79e5c914662c2cf98b4a729c0fcc8c872eaf92e4a595e006b498c44b617ea38f697eca3469
Vendor states this is fixed in 046425412529dbfca1433c8bef5641b271b4ab2a (fixed)
Vendor states this is fixed in 459b59f7ed56511d6529311cb4e5e482ebfcfb8e (fixed)
Vendor states this is fixed in 479a7f90060e62bdd9bb4036ec0a70bf460f6d23 (fixed)
Vendor states this is fixed in c332d9e7dce234d8bef78271d003a68ee943b61b (fixed)
Vendor states this is fixed in cd60992f09b7e83bfd3c76e3bb06b29f3e2fa0a8 (fixed)
Vendor states this is fixed in ea41b5630fa3d9877ce9ed8832cf5575f742bfbb (fixed)
Vendor states this is fixed in f98e894ec029a752cf9c7f7834741bead0fb463d (fixed)
Vendor states this is fixed in fe5c16bb6252dea6025b748257ddc3b2665495b0 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card