CVE-2026-46227: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL
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.10% (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 0c7b55974f97b78d1109025eadf084e74cbf330f, 0dbc8cde64280fc37cdd678cced34eaf96cfb197, 1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078; 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 0c7b55974f97b78d1109025eadf084e74cbf330f, 0dbc8cde64280fc37cdd678cced34eaf96cfb197, 1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078; 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: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.
- BDU:2026-15680
- ALSA-2026:36018
- ALSA-2026:36348
- ALSA-2026:36349
- ALSA-2026:36956
- RHSA-2026:26462
- RHSA-2026:26515
- RHSA-2026:26563
- RHSA-2026:27731
- RHSA-2026:27735
- RHSA-2026:33899
- RHSA-2026:34094
- RHSA-2026:36018
- RHSA-2026:36348
- RHSA-2026:36349
- RHSA-2026:36956
- RHSA-2026:59142
- RHSA-2026:59143
- RHSA-2026:59145
- RHSA-2026:59146
- Published
- May 28, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-416
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 kernel4.17 and later · before 5.10.258
- linux linux kernel5.11 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.90
- linux linux kernel6.13 and later · before 6.18.32
- linux linux kernel6.19 and later · before 7.0.9
- linux linux kernel7.1
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.17affected
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before f3a3f0b406b4b7eb3cea35a23fa2bf170848b104affected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before 0dbc8cde64280fc37cdd678cced34eaf96cfb197affected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before 0c7b55974f97b78d1109025eadf084e74cbf330faffected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before 1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078affected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before 6187a172d6ed57d6b2c327836e4407c6456e639daffected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before c9dadb31f36045a8cb65df4bd75e7237ef21a4b5affected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before bf0f40d8107e2ce827521968dc6926f3e13728aeaffected · git
- 4910280503f3af2857d5aa77e35b22d93a8960a8 and later · before abb5f36771cc4c05899b34000829a787572a8817affected · git
- before 4.17not 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:10 | kernel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.32.1.el10_2 | 6.12.0-211.32.1.el10_2 |
+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-46225May 28, 2026 · spi: rspi: fix controller deregistration22Monitor
- ← EarlierCVE-2026-46226May 28, 2026 · spi: fsl: fix controller deregistration22Monitor
- Later →CVE-2026-46228May 28, 2026 · spi: ch341: fix devres lifetime22Monitor
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 | 0c7b55974f97b78d1109025eadf084e74cbf330f | Vendor (CNA) |
| Linux Linux | 0dbc8cde64280fc37cdd678cced34eaf96cfb197 | Vendor (CNA) |
| Linux Linux | 1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078 | Vendor (CNA) |
| Linux Linux | 6187a172d6ed57d6b2c327836e4407c6456e639d | Vendor (CNA) |
| Linux Linux | abb5f36771cc4c05899b34000829a787572a8817 | Vendor (CNA) |
| Linux Linux | bf0f40d8107e2ce827521968dc6926f3e13728ae | Vendor (CNA) |
| Linux Linux | c9dadb31f36045a8cb65df4bd75e7237ef21a4b5 | Vendor (CNA) |
| Linux Linux | f3a3f0b406b4b7eb3cea35a23fa2bf170848b104 | 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.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.22.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:5.14.0-284.176.1.rt14.461.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
+17
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.
No history yet (it accumulates with the daily EPSS job).
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-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (19 more)Show less
- git.kernel.org/stable/c/0dbc8cde64280fc37cdd678cced34eaf96cfb197
- git.kernel.org/stable/c/1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078
- git.kernel.org/stable/c/6187a172d6ed57d6b2c327836e4407c6456e639d
- git.kernel.org/stable/c/abb5f36771cc4c05899b34000829a787572a8817
- git.kernel.org/stable/c/bf0f40d8107e2ce827521968dc6926f3e13728ae
- git.kernel.org/stable/c/c9dadb31f36045a8cb65df4bd75e7237ef21a4b5
- git.kernel.org/stable/c/f3a3f0b406b4b7eb3cea35a23fa2bf170848b104
- access.redhat.com/errata/RHSA-2026:26462
- access.redhat.com/errata/RHSA-2026:26515
- access.redhat.com/errata/RHSA-2026:26535
- access.redhat.com/errata/RHSA-2026:26563
- access.redhat.com/errata/RHSA-2026:27731
- access.redhat.com/errata/RHSA-2026:27735
- access.redhat.com/errata/RHSA-2026:33899
- access.redhat.com/errata/RHSA-2026:34094
- access.redhat.com/errata/RHSA-2026:36018
- access.redhat.com/errata/RHSA-2026:36348
- access.redhat.com/errata/RHSA-2026:36349
- access.redhat.com/errata/RHSA-2026:36956
Vendor advisories and official records. Exploit/PoC links are deliberately left out.