Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-21718

7.8 · HIGH

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…

Published Feb 27, 2025CWE-362EPSS 0.17%

Overview

CVE-2025-21718 is a high-severity vulnerability. It was published on February 27, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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_timer

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/0d5bca3be27bfcf8f980f2fed49b6cbb7dafe4a1Refgit.kernel.org/stable/c/1409b45d4690308c502c6caf22f01c3c205b4717Refgit.kernel.org/stable/c/1992fb261c90e9827cf5dc3115d89bb0853252c9Refgit.kernel.org/stable/c/51c128ba038cf1b79d605cbee325919b45ab95a5Refgit.kernel.org/stable/c/52f5aff33ca73b2c2fa93f40a3de308012e63cf4Refgit.kernel.org/stable/c/58051a284ac18a3bb815aac6289a679903ddcc3fRefgit.kernel.org/stable/c/5de7665e0a0746b5ad7943554b34db8f8614a196Refgit.kernel.org/stable/c/f55c88e3ca5939a6a8a329024aed8f3d98eea8e4Reflists.debian.org/debian-lts-announce/2025/03/msg00028.htmlReflists.debian.org/debian-lts-announce/2025/05/msg00030.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-21718?

CVE-2025-21718 is a high-severity vulnerability. It was published on February 27, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-21718?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-21718?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-21718?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-21718 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999