tcp: call sk_data_ready() after listener migration
Summary
| CVE | CVE-2026-46015 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-27 14:17:19 UTC |
| Updated | 2026-05-27 14:48:03 UTC |
| 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. |
Risk And Classification
EPSS: 0.000180000 probability, percentile 0.051640000 (date 2026-05-29)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 54b92e84193749c9968aff2dd46e3b0f42643e18 ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b git | Not specified |
| CNA | Linux | Linux | affected 54b92e84193749c9968aff2dd46e3b0f42643e18 bebd058ef40c67a81fe6d9ee8beaa4ede90e0704 git | Not specified |
| CNA | Linux | Linux | affected 54b92e84193749c9968aff2dd46e3b0f42643e18 83bb57635d7cbafde32f865b577ecfd969f02337 git | Not specified |
| CNA | Linux | Linux | affected 54b92e84193749c9968aff2dd46e3b0f42643e18 12625b4da84caf4d84a04988710a7b9bcf702b18 git | Not specified |
| CNA | Linux | Linux | affected 54b92e84193749c9968aff2dd46e3b0f42643e18 3864c6ba1e041bc75342353a70fa2a2c6f909923 git | Not specified |
| CNA | Linux | Linux | affected 5.14 | Not specified |
| CNA | Linux | Linux | unaffected 5.14 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.140 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.86 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.27 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.4 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/bebd058ef40c67a81fe6d9ee8beaa4ede90e0704 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/12625b4da84caf4d84a04988710a7b9bcf702b18 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/83bb57635d7cbafde32f865b577ecfd969f02337 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3864c6ba1e041bc75342353a70fa2a2c6f909923 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.