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-2023-52513RDMA/siw: Fix connection failure handling

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix connection failure handling In case immediate MPA request processing fails, the newly created endpoint unlinks the listening endpoint and is ready to be dropped. This special case was not handled correctly by the code handling the later TCP socket close, causing a NULL dereference crash in siw_cm_work_handler() when dereferencing a NULL listener. We now also cancel the useless MPA timeout, if immediate MPA request processing fails. This patch furthermore simplifies MPA processing in general: Scheduling a useless TCP socket read in sk_data_ready() upcall is now surpressed, if the socket is already moved out of TCP_ESTABLISHED state.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years 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-2023-52513, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.66% · top 48% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 6e26812e289b374c17677d238164a5a8f5770594
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 0d520cdb0cd095eac5d00078dfd318408c9b5eed
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 81b7bf367eea795d259d0261710c6a89f548844d
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 5cf38e638e5d01b68f9133968a85e8b3fd1ecf2f
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < eeafc50a77f6a783c2c44e7ec3674a7b693e06f8
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 53a3f777049771496f791504e7dc8ef017cba590
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.4.258 – ≤ 5.4.*
    • unaffected 5.10.198 – ≤ 5.10.*
    • unaffected 5.15.135 – ≤ 5.15.*
    • unaffected 6.1.57 – ≤ 6.1.*
    • unaffected 6.5.7 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .