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-46015tcp: call sk_data_ready() after listener migration

Description

In the Linux kernel, the following vulnerability has been resolved: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 6 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-2026-46015, 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.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
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 54b92e84193749c9968aff2dd46e3b0f42643e18 – < 7aa7933a5607b1e5b56f322d17265c1d0ea02c51
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < 14e9bb6eba8f59dcc637702e4744ae5e30660d76
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < bebd058ef40c67a81fe6d9ee8beaa4ede90e0704
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < 83bb57635d7cbafde32f865b577ecfd969f02337
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < 12625b4da84caf4d84a04988710a7b9bcf702b18
    • affected 54b92e84193749c9968aff2dd46e3b0f42643e18 – < 3864c6ba1e041bc75342353a70fa2a2c6f909923
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .