Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38377rose: fix dangling neighbour pointers in rose_rt_device_down()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38377, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 94e0918e39039c47ddceb609500817f7266be756
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fe62a35fb1f77f494ed534fc69a9043dc5a30ce1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2b952dbb32fef835756f07ff0cd77efbb836dfea
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < b6b232e16e08c6dc120672b4753392df0d28c1b4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7a1841c9609377e989ec41c16551309ce79c39e4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 446ac00b86be1670838e513b643933d78837d8db
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2c6c82ee074bfcfd1bc978ec45bfea37703d840a
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 34a500caf48c47d5171f4aa1f237da39b07c6157
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.187 – ≤ 5.15.*
    • unaffected 6.1.144 – ≤ 6.1.*
    • unaffected 6.6.97 – ≤ 6.6.*
    • unaffected 6.12.37 – ≤ 6.12.*
    • unaffected 6.15.6 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38377 badge
[![CVE-2025-38377](https://cveledger.app/badge/CVE-2025-38377.svg)](https://cveledger.app/cve/CVE-2025-38377)

Record last updated .