CVE-2025-38377

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.

• CWE-416

• https://git.kernel.org/stable/c/2b952dbb32fef835756f07ff0cd77efbb836dfeaPatch
• https://git.kernel.org/stable/c/2c6c82ee074bfcfd1bc978ec45bfea37703d840aPatch
• https://git.kernel.org/stable/c/34a500caf48c47d5171f4aa1f237da39b07c6157Patch
• https://git.kernel.org/stable/c/446ac00b86be1670838e513b643933d78837d8dbPatch
• https://git.kernel.org/stable/c/7a1841c9609377e989ec41c16551309ce79c39e4Patch
• https://git.kernel.org/stable/c/94e0918e39039c47ddceb609500817f7266be756Patch
• https://git.kernel.org/stable/c/b6b232e16e08c6dc120672b4753392df0d28c1b4Patch
• https://git.kernel.org/stable/c/fe62a35fb1f77f494ed534fc69a9043dc5a30ce1Patch
• https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
• https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory

Published

Jul 25, 2025

Last Modified

Jul 30, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-38371In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38372In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38373In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38374In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38375In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38376In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38378In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-38379In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-3838An Improper Authorization vulnerability was identified in th…6.1
• CVE-2025-38380Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2025-38381In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-38382In the Linux kernel, the following vulnerability has been re…5.5