Skip to main content
EPSS 0.2%top 92%

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix warning in smc_rx_splice() when calling get_page()… (CVE-2025-40012)

0
High
Published: 10/20/2025 (10/20/2025, 18:30:34 UTC)
Source: GCVE Database

Description

A use-after-free vulnerability in the Linux kernel's smc_rx_splice() function was identified and resolved. The issue arises because DMB buffers allocated with kzalloc() are not page-backed, triggering warnings and preventing proper reference counting when passed to get_page(). This can lead to use-after-free if the memory is released prematurely. The fix involves using folio_alloc() to ensure buffers are page-backed and safe for get_page().

CVSS v3.1

Score 7.8high

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/30/2026, 16:09:28 UTC

Technical Analysis

The Linux kernel vulnerability CVE-2025-40012 involves improper memory handling in the smc_rx_splice() function within the smc (Shared Memory Communications) subsystem. Specifically, DMB buffers allocated with kzalloc() are not backed by pages, causing WARN_ON_ONCE() triggers in get_page() and preventing reference counting on these buffers. This flaw can lead to a use-after-free condition if the memory is freed before splice_to_pipe() completes. The issue is resolved by replacing kzalloc() with folio_alloc(), which allocates page-backed memory safe for get_page() operations.

Potential Impact

This vulnerability can cause use-after-free conditions in the Linux kernel's smc subsystem, potentially leading to system instability, crashes, or privilege escalation due to memory corruption. The CVSS 3.1 vector indicates local attack vector with low complexity, requiring low privileges, no user interaction, and results in high confidentiality, integrity, and availability impact.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates that a fix has been implemented by changing the memory allocation method in the kernel source code. Users should monitor official Linux kernel releases and apply updates that include this fix once available.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-c4v9-hjfq-qw76
Osv Schema Version
1.4.0
Aliases
["CVE-2025-40012"]
Database Specific Severity
HIGH
Cvss Version
3.1

Threat ID: 6a6b72d79c2644c7f847b7d4

Added to database: 07/30/2026, 15:50:47 UTC

Last enriched: 07/30/2026, 16:09:28 UTC

Last updated: 09/10/2026, 19:38:48 UTC

Views: 21

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses