CVE-2026-46015: tcp: call sk_data_ready() after listener migration
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12625b4da84caf4d84a04988710a7b9bcf702b18, 14e9bb6eba8f59dcc637702e4744ae5e30660d76, 3864c6ba1e041bc75342353a70fa2a2c6f909923; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12625b4da84caf4d84a04988710a7b9bcf702b18, 14e9bb6eba8f59dcc637702e4744ae5e30660d76, 3864c6ba1e041bc75342353a70fa2a2c6f909923; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-408
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.14 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.86
- linux linux kernel6.13 and later · before 6.18.27
- linux linux kernel6.19 and later · before 7.0.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before 7aa7933a5607b1e5b56f322d17265c1d0ea02c51affected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before 14e9bb6eba8f59dcc637702e4744ae5e30660d76affected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before ab5fdcd535645f6dbe6e9e21d96a08d141e88b4baffected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before bebd058ef40c67a81fe6d9ee8beaa4ede90e0704affected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before 83bb57635d7cbafde32f865b577ecfd969f02337affected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before 12625b4da84caf4d84a04988710a7b9bcf702b18affected · git
- 54b92e84193749c9968aff2dd46e3b0f42643e18 and later · before 3864c6ba1e041bc75342353a70fa2a2c6f909923affected · git
- before 5.14not affected · semver
- 5.15.209 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | kernel | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
| AlmaLinux:9 | kernel-debug-modules-core | before 5.14.0-687.46.1.el9_8 | 5.14.0-687.46.1.el9_8 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46008May 27, 2026 · mm/damon/core: fix damos_walk() vs kdamond_fn() exit race18Monitor
- ← EarlierCVE-2026-46014May 27, 2026 · KVM: SVM: Add missing save/restore handling of LBR MSRs22Monitor
- Later →CVE-2026-46018May 27, 2026 · ALSA: usb-audio: stop parsing UAC2 rates at MAX_NR_RATES22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12625b4da84caf4d84a04988710a7b9bcf702b18 | Vendor (CNA) |
| Linux Linux | 14e9bb6eba8f59dcc637702e4744ae5e30660d76 | Vendor (CNA) |
| Linux Linux | 3864c6ba1e041bc75342353a70fa2a2c6f909923 | Vendor (CNA) |
| Linux Linux | 7aa7933a5607b1e5b56f322d17265c1d0ea02c51 | Vendor (CNA) |
| Linux Linux | 83bb57635d7cbafde32f865b577ecfd969f02337 | Vendor (CNA) |
| Linux Linux | ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b | Vendor (CNA) |
| Linux Linux | bebd058ef40c67a81fe6d9ee8beaa4ede90e0704 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.46.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.52.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+4
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-408 · Incorrect Behavior Order: Early AmplificationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/14e9bb6eba8f59dcc637702e4744ae5e30660d76
- git.kernel.org/stable/c/3864c6ba1e041bc75342353a70fa2a2c6f909923
- git.kernel.org/stable/c/7aa7933a5607b1e5b56f322d17265c1d0ea02c51
- git.kernel.org/stable/c/83bb57635d7cbafde32f865b577ecfd969f02337
- git.kernel.org/stable/c/ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b
- git.kernel.org/stable/c/bebd058ef40c67a81fe6d9ee8beaa4ede90e0704
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.