LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38095: dma-buf: insert memory barrier before updating num_fences

In the Linux kernel, the following vulnerability has been resolved: dma-buf: insert memory barrier before updating num_fences smp_store_mb() inserts memory barrier after storing operation. It is different with what the comment is originally aiming so Null pointer dereference can be happened if memory update is reordered.

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 synchronization error can expose fence-count updates before related memory is ready, potentially causing a null-pointer dereference. Exploitation requires local access with low privileges; it is not described as remotely exploitable. Affected systems could crash, while the supplied CVSS assessment also indicates possible confidentiality and integrity impact.

Executive priority

Prioritize shared Linux systems, endpoints, and compute hosts that run untrusted or low-privileged workloads. This is not presented as an emergency remote compromise, but the high impact score and local low-privilege requirement justify prompt patching through normal high-severity kernel maintenance.

Technical view

The dma-buf fence code used smp_store_mb() with ordering different from the intended comment. CPU memory reordering could make num_fences visible before dependent state, allowing a null-pointer dereference. Stable-kernel commits change the barrier handling. CVSS 3.1 rates it 7.8: local, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is limited to systems running affected Linux kernel builds where a low-privileged local user or workload can reach the vulnerable dma-buf path. Internet accessibility alone does not create direct exposure. The supplied affected-version data is ambiguous and should not be treated as a complete set of clean version ranges.

Exploitation context

The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. The CVSS vector indicates local access and low privileges are required. Public sources supplied here describe the flaw and corrective commits, but do not establish practical exploit reliability or observed attacks.

Researcher notes

The explicit mechanism is a memory-ordering race leading to null-pointer dereference. The source bundle lists repeated commit identifiers and version values without clear range semantics, and provides no CWE. Avoid inferring exposure from version strings alone; evaluate distributor backports. The CVSS impact claims exceed the mechanism detail provided, so broader compromise potential remains insufficiently explained.

Mitigation direction

  • Install the corrected kernel package supplied by your Linux distributor or system vendor.
  • Reboot into the updated kernel after installation; merely installing it may leave the vulnerable kernel running.
  • If updates are unavailable, consult vendor guidance for supported mitigations or backports.
  • Restrict unnecessary local accounts and untrusted workloads until affected systems are updated.

Validation and detection

  • Record the running kernel version and package revision on each potentially affected system.
  • Compare exact vendor builds against distribution advisories, rather than relying only on upstream version numbers.
  • Confirm the applicable stable-kernel correction is included in the installed vendor source or changelog.
  • After rebooting, verify the running kernel matches the corrected package and monitor for kernel fault reports.
Prepared
Confidence
medium
Sources
11

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-38095 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
10Source 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-38095Attack 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
LinuxLinuxa590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63, a590d0fdbaa56f482ff515e1040b6d9b1b200d63unaffected
LinuxLinux5.0, 0, 5.10.241, 5.15.192, 6.1.140, 6.6.92, 6.12.30, 6.14.8, 6.15affected
Weakness

CWE details

No CWE listed

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