LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU

In the Linux kernel, the following vulnerability has been resolved: ipc: fix to protect IPCS lookups using RCU syzbot reported that it discovered a use-after-free vulnerability, [0] [0]: https://lore.kernel.org/all/67af13f8.050a0220.21dd3.0038.GAE@google.com/ idr_for_each() is protected by rwsem, but this is not enough. If it is not protected by RCU read-critical region, when idr_for_each() calls radix_tree_node_free() through call_rcu() to free the radix_tree_node structure, the node will be freed immediately, and when reading the next node in radix_tree_for_each_slot(), the already freed memory may be read. Therefore, we need to add code to make sure that idr_for_each() is protected within the RCU read-critical region when we call it in shm_destroy_orphaned().

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel race can access memory after it has been freed while cleaning up orphaned shared-memory objects. A local, low-privileged user may be able to trigger it without user interaction, potentially affecting confidentiality, integrity, or availability. The supplied evidence does not establish practical exploitation.

Executive priority

Treat as a high-priority kernel update, especially on shared systems, developer platforms, and container hosts running untrusted workloads. It is less urgent for systems without meaningful local access, but should remain in normal expedited patching because successful memory corruption could have severe consequences.

Technical view

The flaw occurs in shm_destroy_orphaned() when idr_for_each() traverses IPC identifiers without an RCU read-side critical section. A radix-tree node can be released through call_rcu(), allowing traversal to read freed memory. Stable-kernel commits add the required RCU protection.

Likely exposure

Exposure is limited to systems running affected Linux kernels where an untrusted or compromised local account can reach the relevant System V shared-memory cleanup path. The supplied version data is ambiguous, so confirm exposure using distribution package advisories and stable-kernel commit ancestry rather than version strings alone.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. Discovery came from syzbot testing. The bundle marks this CVE as absent from KEV, and no supplied source confirms active exploitation, a public exploit, or demonstrated privilege escalation.

Researcher notes

Evidence supports a race-driven use-after-free in Linux IPC identifier traversal and a narrow RCU-protection fix. CVSS scores potential confidentiality, integrity, and availability impact as high, but the supplied sources do not demonstrate reliable exploitation or a specific security outcome. Distribution backports may make upstream version comparisons unreliable.

Mitigation direction

  • Install the vendor-supported kernel package containing the CVE-2025-38212 correction.
  • Reboot into the updated kernel after installation.
  • Prioritize multi-user systems and workloads permitting untrusted local code execution.
  • If updates cannot be applied promptly, request temporary mitigation guidance from the Linux distribution vendor.

Validation and detection

  • Inventory running kernel versions across physical hosts, virtual machines, and container hosts.
  • Compare installed packages with applicable distribution security advisories.
  • Verify the running kernel includes the relevant stable-kernel correction or backport.
  • Confirm systems booted the updated kernel after remediation.
  • Review local access and untrusted workload exposure while remediation remains pending.
Prepared
Confidence
high
Sources
7

Public sources used

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-38212 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
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
12Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53, b34a6b1da371ed8af1221459a18c67970f7e3d53unaffected
LinuxLinux3.1, 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4, 6.16affected
Weakness

CWE details

No CWE listed

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