Review reviewHigh

CVE-2025-38377

Linux Linux, linux kernel, debian linux

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 be...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.07.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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 be...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 94e0918e39039c47ddceb609500817f7266be756, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fe62a35fb1f77f494ed534fc69a9043dc5a30ce1, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2b952dbb32fef835756f07ff0cd77efbb836dfea, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b6b232e16e08c6dc120672b4753392df0d28c1b4, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7a1841c9609377e989ec41c16551309ce79c39e4, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 446ac00b86be1670838e513b643933d78837d8db, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2c6c82ee074bfcfd1bc978ec45bfea37703d840a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 34a500caf48c47d5171f4aa1f237da39b07c6157, >= 2.6.12, >= 2.6.13 < 5.4.296, >= 5.5 < 5.10.240, >= 5.11 < 5.15.187, >= 5.16 < 6.1.144, >= 6.2 < 6.6.97, >= 6.7 < 6.12.37, >= 6.13 < 6.15.6, 2.6.12, 6.16, 11.0
Fixed versions
5.4.296, 5.10.240, 5.15.187, 6.1.144, 6.6.97, 6.12.37, 6.15.6

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416