CVE-2025-21718 — net: rose: fix timer races against user threads
In the Linux kernel, the following vulnerability has been resolved: net: rose: fix timer races against user threads Rose timers only acquire the socket spinlock, without checking if the socket is owned by one user thread. Add a check and rearm the timers if needed. BUG: KASAN: slab-use-after-free in rose_timer_expiry+0x31d/0x360 net/rose/rose_timer.c:174 Read of size 2 at addr ffff88802f09b82a by task swapper/0/0 CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.13.0-rc5-syzkaller-00172-gd1bf27c4e176 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x169/0x550 mm/kasan/report.c:489 kasan_report+0x143/0x180 mm/kasan/report.c:602 rose_timer_expiry+0x31d/0x360 net/rose/rose_timer.c:174 call_timer_fn+0x187/0x650 kernel/time/timer.c:1793 expire_timers kernel/time/timer.c:1844 [inline] __run_timers kernel/time/timer.c:2418 [inline] __run_timer_base+0x66a/0x8e0 kernel/time/timer.c:2430 run_timer_base kernel/time/timer.c:2439 [inline] run_timer_softirq+0xb7/0x170 kernel/time/timer.c:2449 handle_softirqs+0x2d4/0x9b0 kernel/softirq.c:561 __do_softirq kernel/softirq.c:595 [inline] invoke_softirq kernel/softirq.c:435 [inline] __irq_exit_rcu+0xf7/0x220 kernel/softirq.c:662 irq_exit_rcu+0x9/0x30 kernel/softirq.c:678 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1049 </IRQ>
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 52f5aff33ca73b2c2fa93f40a3de308012e63cf4≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0d5bca3be27bfcf8f980f2fed49b6cbb7dafe4a1≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 1409b45d4690308c502c6caf22f01c3c205b4717≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < f55c88e3ca5939a6a8a329024aed8f3d98eea8e4≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 51c128ba038cf1b79d605cbee325919b45ab95a5≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 1992fb261c90e9827cf5dc3115d89bb0853252c9≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 58051a284ac18a3bb815aac6289a679903ddcc3f≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5de7665e0a0746b5ad7943554b34db8f8614a196 and 1 moreversion 2.6.12 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 2.6.12 and < 6.1.129≥ 6.2 and < 6.6.76≥ 6.7 and < 6.12.13≥ 6.13 and < 6.13.2 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 7.0 | CVSS 3.1 | High | 1.0 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.0 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- Affected products added · linux/linux kernel
- CVSS changed · 7.0
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
14 on the record
- git.kernel.org/stable/c/51c128ba038cf1b79d605cbee325919b45ab95a5
- git.kernel.org/stable/c/f55c88e3ca5939a6a8a329024aed8f3d98eea8e4
- git.kernel.org/stable/c/5de7665e0a0746b5ad7943554b34db8f8614a196
- git.kernel.org/stable/c/1992fb261c90e9827cf5dc3115d89bb0853252c9
- git.kernel.org/stable/c/58051a284ac18a3bb815aac6289a679903ddcc3f
- git.kernel.org/stable/c/1409b45d4690308c502c6caf22f01c3c205b4717
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- github.com/advisories/GHSA-qh7w-ppc3-hj63
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- git.kernel.org/stable/c/0d5bca3be27bfcf8f980f2fed49b6cbb7dafe4a1
- nvd.nist.gov/vuln/detail/CVE-2025-21718
- git.kernel.org/stable/c/52f5aff33ca73b2c2fa93f40a3de308012e63cf4
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-21718 is "net: rose: fix timer races against user threads", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.