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-52654io_uring/af_unix: disable sending io_uring over sockets

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/af_unix: disable sending io_uring over sockets File reference cycles have caused lots of problems for io_uring in the past, and it still doesn't work exactly right and races with unix_stream_read_generic(). The safest fix would be to completely disallow sending io_uring files via sockets via SCM_RIGHT, so there are no possible cycles invloving registered files and thus rendering SCM accounting on the io_uring side unnecessary.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months 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-52654, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.89% · top 40% of all CVEs (17 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.8.

Affected products

  • Linux · Linux

    • affected 04df9719df1865f6770af9bc7880874af0e594b2 – < 18824f592aad4124d79751bbc1500ea86ac3ff29
    • affected c378c479c5175833bb22ff71974cda47d7b05401 – < 3fe1ea5f921bf5b71cbfdc4469fb96c05936610e
    • affected 813d8fe5d30388f73a21d3a2bf46b0a1fd72498c – < bcedd497b3b4a0be56f3adf7c7542720eced0792
    • affected 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80 – < f2f57f51b53be153a522300454ddb3887722fb2c
    • affected 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80 – < 5a33d385eb36991a91e3dddb189d8679e2aac2be
    • affected 0091bfc81741b8d3aeb3b7ab8636f911b2de6e80 – < 705318a99a138c29a512a72c3e0043b3cd7f55f4
    • affected b4293c01ee0d0ecdd3cb5801e13f62271144667a
    • affected 75e94c7e8859e58aadc15a98cc9704edff47d4f2
    • affected 5.4.220 – < 5.4.264
    • affected 5.10.150 – < 5.10.204
    • affected 5.15.75 – < 5.15.143
    • affected 5.19.17 – < 5.20
    • affected 6.0.3 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 5.4.264 – ≤ 5.4.*
    • unaffected 5.10.204 – ≤ 5.10.*
    • unaffected 5.15.143 – ≤ 5.15.*
    • unaffected 6.1.68 – ≤ 6.1.*
    • unaffected 6.6.7 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .