System hang via unlocked concurrent ROSE binds
Published Feb 27, 2025 · Updated May 11, 2026
Denial of service in the Linux kernel's ROSE networking code allows local users to hang the system by racing concurrent socket bind calls. rose_bind() changes the socket's binding state without holding its socket lock, allowing concurrent bind operations to conflict with rose_loopback_timer(). Local low-privileged access and enabled ROSE protocol support are required; successful exploitation causes a soft lockup and interrupts service.
Summary
What happened
Denial of service in the Linux kernel's ROSE networking code allows local users to hang the system by racing concurrent socket bind calls. rose_bind() changes the socket's binding state without holding its socket lock, allowing concurrent bind operations to conflict with rose_loopback_timer(). Local low-privileged access and enabled ROSE protocol support are required; successful exploitation causes a soft lockup and interrupts service.
The record
- CVE
- CVE-2025-21749
- Published
- Feb 27, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4c04b0ab3a647e76d0e752b013de8e404abafc63
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <667f61b3498df751c8b3f0be1637e7226cbe3ed0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <970cd2ed26cdab2b0f15b6d90d7eaa36538244a5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a1300691aed9ee852b0a9192e29e2bdc2411a7e6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b8bf5c3fb778bbb1f3ff7d98ec577c969f687513
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d308661a0f4e7c8e86dfc7074a55ee5894c61538
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0384efd45f615603e6869205b72040c209e69cc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ed00c5f907d08a647b8bf987514ad8c6b17971a7
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo