Review reviewCritical

CVE-2026-53355

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: net: rds: clear i_sends on setup unwind The RDS IB connection teardown path is written so it can run during partial startup and on repeated shutdown attempts. It uses NULL pointers to distinguish resources that are still owned from resources that have already been released. When rds_ib_setup_qp() fails after allocating i_sends but before allocating i_recvs, the sends_out path frees i_sends without clearing the pointer. A later shutdown pass can still treat that stale pointer as a live send ring allocation. Clear i_sends aft...

CVSS
9.8
EPSS
0.40%
32.6% percentile
CISA KEV
Not listed
Published
2026.07.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.40%
Technical severityCVSS 9.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net: rds: clear i_sends on setup unwind The RDS IB connection teardown path is written so it can run during partial startup and on repeated shutdown attempts. It uses NULL pointers to distinguish resources that are still owned from resources that have already been released. When rds_ib_setup_qp() fails after allocating i_sends but before allocating i_recvs, the sends_out path frees i_sends without clearing the pointer. A later shutdown pass can still treat that stale pointer as a live send ring allocation. Clear i_sends aft...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 66cccec111421a10efdc2c74499d15b93e7acae5, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 2c5e5e4a5970c41f16e3ad801a78719ed5d5c71b, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 29d940026dce39e3018dab6f67c9427249321270, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < e7cf30aa5f1fc6c2a86df65df8b731df20e44d79, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < f16ad421a4e3e7db2d14bdf3b16f583bc4f3b30a, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 1d4ec754ee3871f7e3670c67bb0298c9c5760926, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 27040bbca289a704eafcacca167d310c6ce2b1bc, >= 3b12f73a5c2977153f28a224392fd4729b50d1dc < 20cf0fb715c41111469577e85e35d15f099473e0, >= 75a12b2fa80c2e4cc40a9f9305f95899850b7426, >= c9459693fae9a1bf3f51f3db98617f694112e897, >= 13099ee9c7d54b0a25f6c8397675aed99e9cfa45, >= 5c6712ab4efb6cf60e16719ab6bcaface9cc268c, >= 3.18.74 < 3.19, >= 4.1.46 < 4.2, >= 4.4.91 < 4.5, >= 4.9.54 < 4.10, >= 4.11, >= 4.11.1 < 5.10.259, >= 5.11 < 5.15.210, >= 5.16 < 6.1.176
Fixed versions
3.19, 4.2, 4.5, 4.10, 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-476