CVE-2025-21749 json
net: rose: lock the socket in rose_bind()
published 2025-02-27 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-5184
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: rose: lock the socket in rose_bind()
syzbot reported a soft lockup in rose_loopback_timer(), with a repro calling bind() from multiple threads.
rose_bind() must lock the socket to avoid this issue.
Patch / fix
- Linux Linux 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14, 6.13.3, 6.14
- linux Debian 12 6.1.129-1
- linux Debian 14, Debian 13 6.12.15-1
debian advisories DEBIAN-CVE-2025-21749
- linux Ubuntu 20.04 LTS 5.4.0-216.236
- linux Ubuntu 22.04 LTS 5.15.0-140.150
- linux Ubuntu 24.04 LTS 6.8.0-64.67
- linux-aws Ubuntu 20.04 LTS 5.4.0-1146.156
- linux-aws Ubuntu 22.04 LTS 5.15.0-1084.91
- linux-aws Ubuntu 24.04 LTS 6.8.0-1032.34
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1149.158
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1083.92
ubuntu advisories UBUNTU-CVE-2025-21749
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
- kernel-syms-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
- kernel-coco_debug SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
- kernel-source-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
- kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
- kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
- kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
- kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1.21.6
suse advisories SUSE-SU-2025:01919-1SUSE-SU-2025:20192-1SUSE-SU-2025:20270-1SUSE-SU-2025:20190-1SUSE-SU-2025:20260-1SUSE-SU-2025:1180-1
- git.kernel.org/stable/c/b8bf5c3fb778bbb1f3ff7d98ec577c969f687513 commit
- git.kernel.org/stable/c/ed00c5f907d08a647b8bf987514ad8c6b17971a7 commit
- git.kernel.org/stable/c/d308661a0f4e7c8e86dfc7074a55ee5894c61538 commit
- git.kernel.org/stable/c/667f61b3498df751c8b3f0be1637e7226cbe3ed0 commit
- git.kernel.org/stable/c/e0384efd45f615603e6869205b72040c209e69cc commit
- git.kernel.org/stable/c/970cd2ed26cdab2b0f15b6d90d7eaa36538244a5 commit
- git.kernel.org/stable/c/4c04b0ab3a647e76d0e752b013de8e404abafc63 commit
- git.kernel.org/stable/c/a1300691aed9ee852b0a9192e29e2bdc2411a7e6 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-21749 updated cvss 5.5
kernel: net: rose: lock the socket in rose_bind()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
- git.kernel.org /stable/c/b8bf5c3fb778bbb1f3ff7d98ec577c969f687513
- git.kernel.org /stable/c/ed00c5f907d08a647b8bf987514ad8c6b17971a7
- git.kernel.org /stable/c/d308661a0f4e7c8e86dfc7074a55ee5894c61538
-
git.kernel.org
/stable/c/667f61b3498df751c8b3f0be1637e7226cbe3ed0
patch
-
git.kernel.org
/stable/c/e0384efd45f615603e6869205b72040c209e69cc
patch
-
git.kernel.org
/stable/c/970cd2ed26cdab2b0f15b6d90d7eaa36538244a5
patch
-
git.kernel.org
/stable/c/4c04b0ab3a647e76d0e752b013de8e404abafc63
patch
-
git.kernel.org
/stable/c/a1300691aed9ee852b0a9192e29e2bdc2411a7e6
patch
- lists.debian.org /debian-lts-announce/2025/05/msg00030.html
- lists.debian.org /debian-lts-announce/2025/03/msg00028.html
Sources
- CVE List CVE-2025-21749
- NVD CVE-2025-21749
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.