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-53355net: rds: clear i_sends on setup unwind

Description

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 after vfree() in the error unwind path so the existing shutdown logic continues to use the correct ownership state.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 35 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-53355, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.42% · top 63% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 66cccec111421a10efdc2c74499d15b93e7acae5
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 2c5e5e4a5970c41f16e3ad801a78719ed5d5c71b
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 29d940026dce39e3018dab6f67c9427249321270
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < e7cf30aa5f1fc6c2a86df65df8b731df20e44d79
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < f16ad421a4e3e7db2d14bdf3b16f583bc4f3b30a
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 1d4ec754ee3871f7e3670c67bb0298c9c5760926
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 27040bbca289a704eafcacca167d310c6ce2b1bc
    • affected 3b12f73a5c2977153f28a224392fd4729b50d1dc – < 20cf0fb715c41111469577e85e35d15f099473e0
    • affected 75a12b2fa80c2e4cc40a9f9305f95899850b7426
    • affected c9459693fae9a1bf3f51f3db98617f694112e897
    • affected 13099ee9c7d54b0a25f6c8397675aed99e9cfa45
    • affected 5c6712ab4efb6cf60e16719ab6bcaface9cc268c
    • affected 3.18.74 – < 3.19
    • affected 4.1.46 – < 4.2
    • affected 4.4.91 – < 4.5
    • affected 4.9.54 – < 4.10
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .