LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38653: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al

In the Linux kernel, the following vulnerability has been resolved: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al Check pde->proc_ops->proc_lseek directly may cause UAF in rmmod scenario. It's a gap in proc_reg_open() after commit 654b33ada4ab("proc: fix UAF in proc_get_inode()"). Followed by AI Viro's suggestion, fix it in same manner.

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

Security readout for executives and security teams

Plain-English summary

A flaw in Linux procfs can access kernel data after it has been freed when a module is removed. A low-privileged local user or process may be able to trigger serious system compromise. It is not remotely exploitable by the CVSS assessment, and active exploitation is not established.

Executive priority

Prioritize normal high-severity kernel patching, accelerating internet-facing multi-user hosts, shared compute, and systems running untrusted workloads. This is not a remote pre-authentication issue, and no active exploitation is documented, but successful use could affect confidentiality, integrity, and availability.

Technical view

The procfs open path checked pde->proc_ops->proc_lseek directly, leaving a use-after-free race during rmmod. The issue was a gap following an earlier proc_get_inode() correction. Upstream stable commits apply the same protected handling used for proc_read_iter and related operations. CVSS 3.1 is 7.8: local, low complexity, low privileges, no interaction.

Likely exposure

Exposure applies to Linux systems running affected kernels where a low-privileged local process can interact with procfs while a relevant kernel module is being removed. The supplied version data names multiple 6.x release markers but lacks sufficiently clear range semantics; confirm exposure through kernel or distribution advisories and fix-commit ancestry.

Exploitation context

The supplied assessment requires local access and low privileges. Triggering also depends on a module-removal race involving proc_lseek. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The key condition is a use-after-free window between procfs operation access and rmmod. Review proc_reg_open() synchronization and determine which stable fix corresponds to each kernel branch. The bundled affected-version array is ambiguous and includes duplicated commit identifiers, so do not infer exact vulnerable ranges without vendor branch mapping.

Mitigation direction

  • Apply a vendor kernel update incorporating the applicable upstream stable fix commit.
  • For Debian LTS systems, follow the cited Debian advisory and install its corrected kernel package.
  • Reduce untrusted local code execution and unnecessary module unload operations until systems are patched.
  • Reboot after updating, then confirm the corrected kernel is actively running.

Validation and detection

  • Inventory running kernel versions across hosts, virtual machines, containers, and appliances.
  • Map each distribution kernel to its vendor advisory and corrected package version.
  • Check kernel source or package metadata for the applicable referenced stable commit.
  • Identify systems permitting low-privileged local code execution or routine module unloading.
  • After remediation, verify the running kernel rather than only the installed package.
Prepared
Confidence
medium
Sources
9

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-38653 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
1ADP providers
8Source 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-38653Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3f61631d47f115b83c935d0039f95cb68b0c8ab7, 3f61631d47f115b83c935d0039f95cb68b0c8ab7, 3f61631d47f115b83c935d0039f95cb68b0c8ab7, 3f61631d47f115b83c935d0039f95cb68b0c8ab7, 3f61631d47f115b83c935d0039f95cb68b0c8ab7, 3f61631d47f115b83c935d0039f95cb68b0c8ab7unaffected
LinuxLinux6.0, 0, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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