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-2022-50555tipc: fix a null-ptr-deref in tipc_topsrv_accept

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: fix a null-ptr-deref in tipc_topsrv_accept syzbot found a crash in tipc_topsrv_accept: KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] Workqueue: tipc_rcv tipc_topsrv_accept RIP: 0010:kernel_accept+0x22d/0x350 net/socket.c:3487 Call Trace: <TASK> tipc_topsrv_accept+0x197/0x280 net/tipc/topsrv.c:460 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 It was caused by srv->listener that might be set to null by tipc_topsrv_stop() in net .exit whereas it's still used in tipc_topsrv_accept() worker. srv->listener is protected by srv->idr_lock in tipc_topsrv_stop(), so add a check for srv->listener under srv->idr_lock in tipc_topsrv_accept() to avoid the null-ptr-deref. To ensure the lsock is not released during the tipc_topsrv_accept(), move sock_release() after tipc_topsrv_work_stop() where it's waiting until the tipc_topsrv_accept worker to be done. Note that sk_callback_lock is used to protect sk->sk_user_data instead of srv->listener, and it should check srv in tipc_topsrv_listener_data_ready() instead. This also ensures that no more tipc_topsrv_accept worker will be started after tipc_conn_close() is called in tipc_topsrv_stop() where it sets sk->sk_user_data to null.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 10 months 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-2022-50555, 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.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.22% · top 87% of all CVEs (15 Nov 2026)
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 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < ce69bdac2310152bb70845024d5d704c52aabfc3
    • affected 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < 24b129aed8730e48f47d852d58d76825ab6f407c
    • affected 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < 32a3d4660b34ce49ac0162338ebe362098e2f5df
    • affected 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < 7a939503fc32bff4ed60800b73ff7fbb4aea2142
    • affected 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < cedb41664e27b2cae7e21487f1bee22dcd84037d
    • affected 0ef897be12b8b4cf297b6016e79ec97ec90f2cf6 – < 82cb4e4612c633a9ce320e1773114875604a3cce
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 4.19.264 – ≤ 4.19.*
    • unaffected 5.4.223 – ≤ 5.4.*
    • unaffected 5.10.153 – ≤ 5.10.*
    • unaffected 5.15.77 – ≤ 5.15.*
    • unaffected 6.0.7 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .