LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21766: ipv4: use RCU protection in __ip_rt_update_pmtu()

In the Linux kernel, the following vulnerability has been resolved: ipv4: use RCU protection in __ip_rt_update_pmtu() __ip_rt_update_pmtu() must use RCU protection to make sure the net structure it reads does not disappear.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux IPv4 networking race could let a kernel network structure disappear while still being read. Successful exploitation may compromise confidentiality, integrity, and availability, but requires difficult timing conditions. Prioritize affected internet-facing and critical Linux systems.

Executive priority

Treat as a high-priority kernel update, especially for exposed or shared infrastructure. Accelerate remediation where compromise would disrupt critical services or sensitive data. Current sources do not support an emergency response based on active exploitation, but the potential impact justifies timely patching.

Technical view

The kernel function __ip_rt_update_pmtu() accessed a network namespace structure without required RCU lifetime protection. Concurrent teardown could invalidate that structure during use. The upstream correction adds RCU protection. CVSS 3.1 scores it 8.1: network-reachable, no privileges or user interaction, but high attack complexity.

Likely exposure

Exposure applies to Linux systems running affected kernels or vendor products incorporating them, particularly where IPv4 networking is active. The supplied version data mixes releases and commit identifiers, so distribution package versions cannot be judged by upstream numbers alone. Vendor backport status must be checked.

Exploitation context

The CVSS vector describes network reachability with no privileges or user interaction, but high complexity. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Treat exploitation status as unconfirmed, not impossible.

Researcher notes

The core issue is a lifetime-synchronization failure involving a net structure in IPv4 PMTU handling. No CWE is supplied. Version records are ambiguous because they combine commits and releases; validate reachability through vendor package provenance and backports. The sources establish a fix but do not establish practical exploitability or observed attacks.

Mitigation direction

  • Install a vendor-supported kernel update containing the upstream RCU fix.
  • Consult Linux distribution advisories for package-specific fixed versions and backport status.
  • Review Siemens guidance before updating any affected Siemens product or appliance.
  • Prioritize internet-facing, multi-tenant, and business-critical Linux systems.
  • Use vendor-recommended compensating controls if immediate patching is unavailable.

Validation and detection

  • Inventory running kernel and distribution package versions across Linux systems.
  • Compare packages against distribution advisories, not upstream version numbers alone.
  • Confirm the installed update contains the __ip_rt_update_pmtu() RCU correction.
  • Reboot updated systems when required, then verify the active kernel version.
  • Check affected Siemens assets against SSA-082556 and applicable product versions.
Prepared
Confidence
medium
Sources
5

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-21766 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
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-21766Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2fbc6e89b2f1403189e624cabaf73e189c5e50c6, 2fbc6e89b2f1403189e624cabaf73e189c5e50c6, 2fbc6e89b2f1403189e624cabaf73e189c5e50c6, 2fbc6e89b2f1403189e624cabaf73e189c5e50c6, 2fbc6e89b2f1403189e624cabaf73e189c5e50c6, 2fbc6e89b2f1403189e624cabaf73e189c5e50c6, f415c264176e6095e9dee823e09c5bdd0ee0d337, 98776a365da509ad923083ae54b38ee521c52742, 860e2cc78c697c95bc749abb20047239fa1722ea, 2b1be6c925cdf4638811765a9160796291494b89, 4.14.200, 4.19.148, 5.4.68, 5.8.12unaffected
LinuxLinux5.9, 0, 5.15.179, 6.1.129, 6.6.79, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

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