Use-after-free via SCTP timer reference race
Published Sep 25, 2026 · Updated Sep 25, 2026
Use-after-free in Linux kernel SCTP handling allows attackers to trigger stale association access by racing a timer during teardown. SCTP_CMD_TIMER_START separately checks timer_pending() and calls timer_reduce(), allowing an expired timer to be rearmed without acquiring the association reference later dropped by its callback. Reachability requires winning that timer-expiration race during association teardown; the published record establishes use-after-free but does not document code execution or data disclosure.
Summary
What happened
Use-after-free in Linux kernel SCTP handling allows attackers to trigger stale association access by racing a timer during teardown. SCTP_CMD_TIMER_START separately checks timer_pending() and calls timer_reduce(), allowing an expired timer to be rearmed without acquiring the association reference later dropped by its callback. Reachability requires winning that timer-expiration race during association teardown; the published record establishes use-after-free but does not document code execution or data disclosure.
The record
- CVE
- CVE-2026-98130
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=085bb270b4b1168c93afb37bbafc881207d15443
- Affected versionversion=20a785aa52c82246055a089e55df9dac47d67da1 <00b841bac10230c557be6b38efc48508198fe23e
- Affected versionversion=20a785aa52c82246055a089e55df9dac47d67da1 <2188569e7e1b0bc3f3b557dc97ab7a02befc11c8
- Affected versionversion=20a785aa52c82246055a089e55df9dac47d67da1 <3d698d1e6c8bc41e3e1707777a016f1bdd07842d
- Affected versionversion=20a785aa52c82246055a089e55df9dac47d67da1 <e42ba56281ca3ae2dcb3558bebee9a1c9a4831d9
- Affected versionversion=4.19.126 <4.20
- Affected versionversion=5.4.44 <5.5
- Affected versionversion=5.6.16 <5.7
- Affected versionversion=5.7
- Affected versionversion=70989e501fbce502198d82da88358ce453575a05
- Affected versionversion=9c0a4652f750afe3b4468cbcd9335b244ce2facd
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started