CVE-2025-38377
rose: fix dangling neighbour pointers in rose_rt_device_down()
Reported by linux · Published July 25, 2025
In the Linux kernel, the following vulnerability has been resolved: rose: fix dangling neighbour pointers in rose_rt_device_down() There are two bugs in rose_rt_device_down() that can cause use-after-free: 1. The loop bound `t->count` is modified within the loop, which can cause the loop to terminate early and miss some entries. 2. When removing an entry from the neighbour array, the subsequent entries are moved up to fill the gap, but the loop index `i` is still incremented, causing the next entry to be skipped. For example, if a node has three neighbours (A, A, B) with count=3 and A is being removed, the second A is not checked. i=0: (A, A, B) -> (A, B) with count=2 ^ checked i=1: (A, B) -> (A, B) with count=2 ^ checked (B, not A!) i=2: (doesn't occur because i < count is false) This leaves the second A in the array with count=2, but the rose_neigh structure has been freed. Code that accesses these entries assumes that the first `count` entries are valid pointers, causing a use-after-free when it accesses the dangling pointer. Fix both issues by iterating over the array in reverse order with a fixed loop bound. This ensures that all entries are examined and that the removal of an entry doesn't affect subsequent iterations.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.15.6, 6.12.37, 6.6.97, 6.1.144, 5.15.187, 5.10.240, 5.4.296 |
| Linux | Linux | fe62a35fb1f77f494ed534fc69a9043dc5a30ce1, b6b232e16e08c6dc120672b4753392df0d28c1b4, 7a1841c9609377e989ec41c16551309ce79c39e4, 446ac00b86be1670838e513b643933d78837d8db, 34a500caf48c47d5171f4aa1f237da39b07c6157, 2c6c82ee074bfcfd1bc978ec45bfea37703d840a, 2b952dbb32fef835756f07ff0cd77efbb836dfea |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| Linux | Linux | 2.6.12, 0, 5.4.296 |
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 5.10.240, 5.15.187 |
| linux | linux_kernel | 2.6.12, 2.6.12, 2.6.12 |
Timeline
- Jul 25, 2025 CVE Published
- Jul 26, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (10 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (243 in total, the first dated here)
- Mar 29, 2026 Security Advisory (260 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
- Oct 7, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38377
vulnetix vdb fixes CVE-2025-38377
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38377/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart