CVE-2026-72383: sctp: fix addr_wq_timer race in sctp_free_addr_wq()
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.16% (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 5098308ad72f83f3b1a48c247dddab1695114bae, 976c19de0f22a857ba0112f39635f8fd7a257568, a8323fb2ab6cd6978f359daeed6688e0cadf32ba; 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 5098308ad72f83f3b1a48c247dddab1695114bae, 976c19de0f22a857ba0112f39635f8fd7a257568, a8323fb2ab6cd6978f359daeed6688e0cadf32ba; 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: fix addr_wq_timer race in sctp_free_addr_wq() sctp_free_addr_wq() previously removed addr_wq_timer using timer_delete() while holding addr_wq_lock. However, timer_delete() does not guarantee that a currently running timer handler has completed. This allows a race with sctp_addr_wq_timeout_handler(), where the handler may still run after addr_waitq has been freed, acquire addr_wq_lock, and access freed memory, leading to a use-after-free. Fix this by calling timer_shutdown_sync() before taking addr_wq_lock. This guarantees that any in-flight timer handler has finished and prevents the timer from being re-armed during teardown, making subsequent cleanup safe.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
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.
—
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
- 3.7affected
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before fb6117713abef8646fdbf58256532451bcf26c47affected · git
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before 5098308ad72f83f3b1a48c247dddab1695114baeaffected · git
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before d49eff15261dd62e4fa3a316c26cb1f537a60464affected · git
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before a8323fb2ab6cd6978f359daeed6688e0cadf32baaffected · git
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1affected · git
- 4db67e808640e3934d82ce61ee8e2e89fd877ba8 and later · before 976c19de0f22a857ba0112f39635f8fd7a257568affected · git
- before 3.7not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*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 |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72380Aug 15, 2026 · xen/pvcalls: bound backend response req_id before indexing rsp[]35Monitor
- ← EarlierCVE-2026-72382Aug 15, 2026 · ksmbd: reject undersized DACLs before parsing ACEs35Monitor
- Later →CVE-2026-72388Aug 15, 2026 · drm/panthor: Always use the IRQ-safe variant when acquiring the fence lock0Monitor
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 | 5098308ad72f83f3b1a48c247dddab1695114bae | Vendor (CNA) |
| Linux Linux | 976c19de0f22a857ba0112f39635f8fd7a257568 | Vendor (CNA) |
| Linux Linux | a8323fb2ab6cd6978f359daeed6688e0cadf32ba | Vendor (CNA) |
| Linux Linux | c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1 | Vendor (CNA) |
| Linux Linux | d49eff15261dd62e4fa3a316c26cb1f537a60464 | Vendor (CNA) |
| Linux Linux | fb6117713abef8646fdbf58256532451bcf26c47 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| 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.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.5-1 · Debian:14 | 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.
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
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)
—
CVSS 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 (5 more)Show less
- git.kernel.org/stable/c/976c19de0f22a857ba0112f39635f8fd7a257568
- git.kernel.org/stable/c/a8323fb2ab6cd6978f359daeed6688e0cadf32ba
- git.kernel.org/stable/c/c3e5cac47519d77ad36b9c03a1df1536aaa0c4a1
- git.kernel.org/stable/c/d49eff15261dd62e4fa3a316c26cb1f537a60464
- git.kernel.org/stable/c/fb6117713abef8646fdbf58256532451bcf26c47
Vendor advisories and official records. Exploit/PoC links are deliberately left out.