NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 2b952dbb32fef835756f07ff0cd77efbb836dfea, 2c6c82ee074bfcfd1bc978ec45bfea37703d840a, 34a500caf48c47d5171f4aa1f237da39b07c6157.

Low priority for now. Upgrade to Linux Linux 2b952dbb32fef835756f07ff0cd77efbb836dfea, 2c6c82ee074bfcfd1bc978ec45bfea37703d840a, 34a500caf48c47d5171f4aa1f237da39b07c6157 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-13512

Published: Jul 25, 2025
Updated: Aug 5, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CNA vs NVD score

NVD: 7.8
CNA · Linux: 8.8; 1.0 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux11.0
linux linux kernel5.5 and later · before 5.10.240
linux linux kernel5.11 and later · before 5.15.187
linux linux kernel5.16 and later · before 6.1.144
linux linux kernel6.2 and later · before 6.6.97
linux linux kernel2.6.13 and later · before 5.4.296
linux linux kernel6.13 and later · before 6.15.6
linux linux kernel6.7 and later · before 6.12.37
linux linux kernel2.6.12
linux linux kernel6.16

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 94e0918e39039c47ddceb609500817f7266be756affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fe62a35fb1f77f494ed534fc69a9043dc5a30ce1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2b952dbb32fef835756f07ff0cd77efbb836dfeaaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b6b232e16e08c6dc120672b4753392df0d28c1b4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7a1841c9609377e989ec41c16551309ce79c39e4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 446ac00b86be1670838e513b643933d78837d8dbaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2c6c82ee074bfcfd1bc978ec45bfea37703d840aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 34a500caf48c47d5171f4aa1f237da39b07c6157affected · git
- before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.147-1	6.1.147-1
Debian:13	linux	before 6.12.37-1	6.12.37-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2025-38374Jul 25, 2025 · optee: ffa: fix sleep in atomic context
22Monitor
← EarlierCVE-2025-38376Jul 25, 2025 · usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume
22Monitor
Later →CVE-2025-38378Jul 25, 2025 · HID: appletb-kbd: fix slab use-after-free bug in appletb_kbd_probe
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	2b952dbb32fef835756f07ff0cd77efbb836dfea	Vendor (CNA)
Linux Linux	2c6c82ee074bfcfd1bc978ec45bfea37703d840a	Vendor (CNA)
Linux Linux	34a500caf48c47d5171f4aa1f237da39b07c6157	Vendor (CNA)
Linux Linux	446ac00b86be1670838e513b643933d78837d8db	Vendor (CNA)
Linux Linux	7a1841c9609377e989ec41c16551309ce79c39e4	Vendor (CNA)
Linux Linux	94e0918e39039c47ddceb609500817f7266be756	Vendor (CNA)
Linux Linux	b6b232e16e08c6dc120672b4753392df0d28c1b4	Vendor (CNA)
Linux Linux	fe62a35fb1f77f494ed534fc69a9043dc5a30ce1	Vendor (CNA)
debian:linux	6.1.147-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/2b952dbb32fef835756f07ff0cd77efbb836dfea

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records