CVE-2021-46999: sctp: do asoc update earlier in sctp_sf_do_dupcook_a
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.74% (FIRST EPSS); higher than 55.2% of all records.
- 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 0bfd913c2121b3d553bfd52810fe6061d542d625, 35b4f24415c854cd718ccdf38dbea6297f010aae, 4.19.191.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0bfd913c2121b3d553bfd52810fe6061d542d625, 35b4f24415c854cd718ccdf38dbea6297f010aae, 4.19.191 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: do asoc update earlier in sctp_sf_do_dupcook_a There's a panic that occurs in a few of envs, the call trace is as below: [] general protection fault, ... 0x29acd70f1000a: 0000 [#1] SMP PTI [] RIP: 0010:sctp_ulpevent_notify_peer_addr_change+0x4b/0x1fa [sctp] [] sctp_assoc_control_transport+0x1b9/0x210 [sctp] [] sctp_do_8_2_transport_strike.isra.16+0x15c/0x220 [sctp] [] sctp_cmd_interpreter.isra.21+0x1231/0x1a10 [sctp] [] sctp_do_sm+0xc3/0x2a0 [sctp] [] sctp_generate_timeout_event+0x81/0xf0 [sctp] This is caused by a transport use-after-free issue. When processing a duplicate COOKIE-ECHO chunk in sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated with the transort from the new asoc. However, later in the sideeffect machine, the old asoc is used to send them out and old asoc's shutdown_last_sent_to is set to the transport that SHUTDOWN chunk attached to in sctp_cmd_setup_t2(), which actually belongs to the new asoc. After the new_asoc is freed and the old asoc T2 timeout, the old asoc's shutdown_last_sent_to that is already freed would be accessed in sctp_sf_t2_timer_expire(). Thanks Alexander and Jere for helping dig into this issue. To fix it, this patch is to do the asoc update first, then allocate the COOKIE-ACK and SHUTDOWN chunks with the 'updated' old asoc. This would make more sense, as a chunk from an asoc shouldn't be sent out with another asoc. We had fixed quite a few issues caused by this.
- Published
- Feb 28, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 9.8
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
Is your version affected? Check itNoroxi 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 |
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
- a5ce8531ea508d270822b2bc6140c6198c8a2a7b, 5.7affected
- db8bf823e70f239372c62f13e4eb6f08a1665e8c and later · before d624f2991b977821375fbd56c91b0c91d456a697affected · git
- a204d577be70e0a0a6023cf1b9859c9ebffaeecd and later · before b1b31948c0af44628e43353828453461bb74098faffected · git
- 145cb2f7177d94bc54563ed26027e952ee0ae03c and later · before f01988ecf3654f805282dce2d3bb9afe68d2691eaffected · git
- 145cb2f7177d94bc54563ed26027e952ee0ae03c and later · before 61b877bad9bb0d82b7d8841be50872557090a704affected · git
- 145cb2f7177d94bc54563ed26027e952ee0ae03c and later · before 0bfd913c2121b3d553bfd52810fe6061d542d625affected · git
- 145cb2f7177d94bc54563ed26027e952ee0ae03c and later · before 35b4f24415c854cd718ccdf38dbea6297f010aaeaffected · git
- 4.19.123 and later · before 4.19.191affected · semver
- 5.4.41 and later · before 5.4.120affected · semver
- 5.6.13 and later · before 5.7affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.19.123 and later · before 4.19.191
- linux linux kernel5.4.41 and later · before 5.4.120
- linux linux kernel5.7 and later · before 5.10.38
- linux linux kernel5.11 and later · before 5.11.22
- linux linux kernel5.12 and later · before 5.12.5
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 | before 5.10.38-1 | 5.10.38-1 |
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-2021-46997Feb 28, 2024 · arm64: entry: always set GIC_PRIO_PSR_I_SET during entry22Monitor
- ← EarlierCVE-2021-46998Feb 28, 2024 · ethernet:enic: Fix a use after free bug in enic_hard_start_xmit31Monitor
- Later →CVE-2021-47000Feb 28, 2024 · ceph: fix inode leak on getattr error in __fh_to_dentry13Monitor
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 | 0bfd913c2121b3d553bfd52810fe6061d542d625 | Vendor (CNA) |
| Linux Linux | 35b4f24415c854cd718ccdf38dbea6297f010aae | Vendor (CNA) |
| Linux Linux | 4.19.191 | Vendor (CNA) |
| Linux Linux | 5.4.120 | Vendor (CNA) |
| Linux Linux | 5.7 | Vendor (CNA) |
| Linux Linux | 61b877bad9bb0d82b7d8841be50872557090a704 | Vendor (CNA) |
| Linux Linux | b1b31948c0af44628e43353828453461bb74098f | Vendor (CNA) |
| Linux Linux | d624f2991b977821375fbd56c91b0c91d456a697 | Vendor (CNA) |
| Linux Linux | f01988ecf3654f805282dce2d3bb9afe68d2691e | Vendor (CNA) |
| debian:linux | 5.10.38-1 · 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.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0145 · Feb 29, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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-primary
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/35b4f24415c854cd718ccdf38dbea6297f010aae
- git.kernel.org/stable/c/61b877bad9bb0d82b7d8841be50872557090a704
- git.kernel.org/stable/c/b1b31948c0af44628e43353828453461bb74098f
- git.kernel.org/stable/c/d624f2991b977821375fbd56c91b0c91d456a697
- git.kernel.org/stable/c/f01988ecf3654f805282dce2d3bb9afe68d2691e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.