LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71086: net: rose: fix invalid array index in rose_kill_by_device()

In the Linux kernel, the following vulnerability has been resolved: net: rose: fix invalid array index in rose_kill_by_device() rose_kill_by_device() collects sockets into a local array[] and then iterates over them to disconnect sockets bound to a device being brought down. The loop mistakenly indexes array[cnt] instead of array[i]. For cnt < ARRAY_SIZE(array), this reads an uninitialized entry; for cnt == ARRAY_SIZE(array), it is an out-of-bounds read. Either case can lead to an invalid socket pointer dereference and also leaks references taken via sock_hold(). Fix the index to use i.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the ROSE networking code. When a network device is brought down, the kernel may read the wrong socket array entry, which can dereference an invalid socket pointer and leak socket references. Business impact is unclear because severity, CVSS, and real-world exploit evidence are not provided.

Executive priority

Treat this as a targeted kernel maintenance issue until vendor severity data improves. Prioritize patch verification on Linux systems with unusual networking modules, embedded deployments, or Siemens-advised exposure, but do not classify it as emergency without exploitation or severity evidence.

Technical view

rose_kill_by_device() gathers sockets into a local array, then disconnects sockets bound to a device. The loop uses array[cnt] instead of array[i], causing an uninitialized read when cnt is below the array size or an out-of-bounds read at the limit. The fix changes the index to i.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the ROSE networking code present and relevant device teardown paths reachable. The source bundle does not identify affected distributions, configurations, or Siemens product impact details beyond the referenced advisory.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit code, or weaponized use. The described failure mode suggests possible kernel instability or resource leakage, but exploitability beyond invalid pointer dereference is not established here.

Researcher notes

The root cause is a wrong loop index in rose_kill_by_device(). The evidence supports invalid read, invalid socket pointer dereference, and sock_hold() reference leaks. The bundle does not include CVSS, CWE, proof of exploitability, distribution advisories, or complete affected configuration details.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and package names.
  • Review the Siemens advisory if Siemens products are in scope.
  • Prioritize systems using or exposing ROSE networking functionality.
  • If no update is available, follow vendor guidance for temporary mitigations.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Map kernels against vendor advisories and referenced stable commits.
  • Confirm whether ROSE networking support is enabled or loaded.
  • Verify patched systems include the corrected rose_kill_by_device() index logic.
  • Track Siemens advisory applicability for managed product environments.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71086 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux12e5a4719c99d7f4104e7e962393dfb8baa1c591, c0e527c532a07556ca44642f5873b002c44da22c, 3e0d1585799d8a991eba9678f297fd78d9f1846e, ffced26692f83212aa09d0ece0213b23cc2f611d, 64b8bc7d5f1434c636a40bdcfcd42b278d1714be, 64b8bc7d5f1434c636a40bdcfcd42b278d1714be, 64b8bc7d5f1434c636a40bdcfcd42b278d1714be, bd7de4734535140fda33240c2335a07fdab6f88e, b10265532df7bc3666bc53261b7f03f0fd14b1c9, 5.10.206, 5.15.146, 6.1.70, 6.6.9, 4.19.304, 5.4.266unaffected
LinuxLinux6.7, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.