CVE-2026-98846: sctp: check RCV_SHUTDOWN after the sendmsg connect wait
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 1bef1944ef15a40797305bf916827b04df6307ca, 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 1bef1944ef15a40797305bf916827b04df6307ca, 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4, 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.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: sctp: check RCV_SHUTDOWN after the sendmsg connect wait sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer. Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed. Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
—
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
- 4.16affected
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before 7f798168c54455559da0f7a377a23ab7019fec35affected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before fe5a23c76fc48b711eb7d6f3462c994e34da36f9affected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4affected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before 1bef1944ef15a40797305bf916827b04df6307caaffected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before e8f972b1759d26bbefe4c524caae1ed7c8a593bdaffected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before e701345d886e831fb593a0870d69c8c5de6fc938affected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669affected · git
- 668c9beb9020d5834ee9e43c208190a07d2b1928 and later · before 4f1da630d13de0370e2f6361f961f1c8b384af1caffected · git
- before 4.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98844Oct 18, 2026 · netfs: clear post-EOF pagecache when extending a file via write0Monitor
- ← EarlierCVE-2026-98845Oct 18, 2026 · tpm: Disable TPM on null key name mismatch0Monitor
- Later →CVE-2026-98847Oct 18, 2026 · rtc: spear: initialize IRQ state before requesting alarm IRQ0Monitor
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 | 1bef1944ef15a40797305bf916827b04df6307ca | Vendor (CNA) |
| Linux Linux | 1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4 | Vendor (CNA) |
| Linux Linux | 222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669 | Vendor (CNA) |
| Linux Linux | 4f1da630d13de0370e2f6361f961f1c8b384af1c | Vendor (CNA) |
| Linux Linux | 7f798168c54455559da0f7a377a23ab7019fec35 | Vendor (CNA) |
| Linux Linux | e701345d886e831fb593a0870d69c8c5de6fc938 | Vendor (CNA) |
| Linux Linux | e8f972b1759d26bbefe4c524caae1ed7c8a593bd | Vendor (CNA) |
| Linux Linux | fe5a23c76fc48b711eb7d6f3462c994e34da36f9 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
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.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+19 d
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).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1e7cd89975fa3b11ebd7e1bbb4648a71c0e0e2d4
- git.kernel.org/stable/c/222c41e0f50f1d5028be9baf0e1dcfc0bfa7f669
- git.kernel.org/stable/c/4f1da630d13de0370e2f6361f961f1c8b384af1c
- git.kernel.org/stable/c/7f798168c54455559da0f7a377a23ab7019fec35
- git.kernel.org/stable/c/e701345d886e831fb593a0870d69c8c5de6fc938
- git.kernel.org/stable/c/e8f972b1759d26bbefe4c524caae1ed7c8a593bd
- git.kernel.org/stable/c/fe5a23c76fc48b711eb7d6f3462c994e34da36f9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.