CVE-2026-46015: tcp: call sk_data_ready() after listener migration
Vulnerability summary
CVE-2026-46015 is a high (CVSS 7.8) vulnerability in linux. EPSS estimates a 0.14% chance of exploitation in the next 30 days, higher than 3% of scored vulnerabilities.
Not severe (CVSS 7.8, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 48 · Related 46Timeline
- 27-05-2026PublishedVulnerability first disclosed.
- 19-10-2026Last modifiedVulnerability information updated.
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.
CVSS metrics
4 scores · 4 sources · 1 version- OSV · UbuntuEcosystem advisory · calculated7.8HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- OSV · DebianEcosystem advisory · calculated7.8HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- NVDNIST7.8HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS trend
Probability
0.14%
Chance of exploitation in the next 30 days
Percentile
3%
Versus all other CVEs
30-day change
Decrease -0.04 pp
From 0.18% on 04-10-2026
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeAffected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu147 products
- linux< 5.15.0-186.196 | < 6.8.0-136.136 | All versions (No fix recorded) | < 7.0.0-27.27
- linux-allwinner-5.19All versions (No fix recorded)
- linux-aws< 5.15.0-1112.119 | < 6.8.0-1061.64 | All versions (No fix recorded) | < 7.0.0-1008.8
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Linux2 products
- linux≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < 7aa7933a5607b1e5b56f322d17265c1d0ea02c51 | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < 14e9bb6eba8f59dcc637702e4744ae5e30660d76 | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < bebd058ef40c67a81fe6d9ee8beaa4ede90e0704 | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < 83bb57635d7cbafde32f865b577ecfd969f02337 | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < 12625b4da84caf4d84a04988710a7b9bcf702b18 | ≥ 54b92e84193749c9968aff2dd46e3b0f42643e18, < 3864c6ba1e041bc75342353a70fa2a2c6f909923 | 5.14
- linux_kernel≥ 5.14, < 5.15.209 | ≥ 5.16, < 6.1.175 | ≥ 6.2, < 6.6.140 | ≥ 6.7, < 6.12.86 | ≥ 6.13, < 6.18.27 | ≥ 6.19, < 7.0.4
Debian1 product
- linux< 6.1.176-1 | < 6.12.86-1 | < 7.0.4-1
3 vendors · 150 products