Kernel memory corruption via uninitialized statmount pointer
Published Dec 16, 2025 · Updated Dec 16, 2025
Uninitialized pointer use in affected Linux kernels allows local users to corrupt kernel memory and trigger a panic through statmount requests. The UIDMAP and GIDMAP branches leave offp uninitialized, so a later four-byte offset write corrupts seq.buf, root.mnt, or another live pointer. An unprivileged local user needs a visible idmapped mount with a resolvable mapping; the corruption can disclose kernel memory, enable code execution, or cause a kernel oops or panic.
Summary
What happened
Uninitialized pointer use in affected Linux kernels allows local users to corrupt kernel memory and trigger a panic through statmount requests. The UIDMAP and GIDMAP branches leave offp uninitialized, so a later four-byte offset write corrupts seq.buf, root.mnt, or another live pointer. An unprivileged local user needs a visible idmapped mount with a resolvable mapping; the corruption can disclose kernel memory, enable code execution, or cause a kernel oops or panic.
The record
- CVE
- CVE-2025-68212
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.14
- Affected versionversion=c3787a4fae66e710543137b4b1b073cb2bff3bca
- Affected versionversion=d49c64c1d723c167f521833f429ab28d3ca7e0d9
- Affected versionversion=e52e97f09fb66fd868260d05bd6b74a9a3db39ee <0778ac7df5137d5041783fadfc201f8fd55a1d9b
- Affected versionversion=e52e97f09fb66fd868260d05bd6b74a9a3db39ee <acfde9400e611c8d2668f1c70053c4a1d6ecfc36
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo