8.8

CVE-2025-38377: debian debian_linux Use After Free

CVSS: 8.8v3.1HighModified
AliasesUBUNTU-CVE-2025-38377DEBIAN-CVE-2025-38377
Published 25-07-2025Last modified 05-08-2026

Vulnerability summary

CVE-2025-38377 is a high (CVSS 8.8) Use After Free vulnerability in debian debian_linux. EPSS estimates a 0.26% chance of exploitation in the next 30 days, higher than 16.9% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.8/10
010
High · v3.1 (CVE.org)
EPSS score
0.26%
0%100%
Low · +0.03 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 53 · Related 47

Timeline

  1. 25-07-2025
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

5 scores · 4 sources · 2 versions

EPSS trend

Probability

0.26%

Chance of exploitation in the next 30 days

Percentile

17%

Versus all other CVEs

30-day change

+0.03 pp

From 0.24% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.26%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu146 products
  • linuxAll versions (No fix recorded) | < 5.15.0-156.166 | < 6.8.0-100.100
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.15.0-1092.99 | < 6.8.0-1046.49
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
Linux2 products
  • linux≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 94e0918e39039c47ddceb609500817f7266be756 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < fe62a35fb1f77f494ed534fc69a9043dc5a30ce1 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2b952dbb32fef835756f07ff0cd77efbb836dfea | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < b6b232e16e08c6dc120672b4753392df0d28c1b4 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 7a1841c9609377e989ec41c16551309ce79c39e4 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 446ac00b86be1670838e513b643933d78837d8db | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2c6c82ee074bfcfd1bc978ec45bfea37703d840a | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 34a500caf48c47d5171f4aa1f237da39b07c6157 | 2.6.12
  • linux_kernel≥ 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 | 2.6.12:rc2 | 2.6.12:rc3 | 2.6.12:rc4 | 2.6.12:rc5 | 6.16:rc1 | 6.16:rc2 | 6.16:rc3 | 6.16:rc4

3 vendors · 150 products

References

45 links
Show all 45 references