CVE-2025-68167
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix invalid pointer access in debugfs If the memory allocation in gpiolib_seq_start() fails, the s->private field remains uninitialized and is later dereferenced without checking in gpiolib_seq_stop(). Initialize s->private to NULL before calling kzalloc() and check it before dereferencing it.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2025-12-18
Generated
2026-06-16
AI Q&A
2025-12-16
EPSS Evaluated
2026-06-15
NVD
CVE-2025-68167
EUVD
EUVD-2025-203729
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's gpiolib debugfs occurs because if memory allocation in the function gpiolib_seq_start() fails, a pointer field (s->private) remains uninitialized. Later, this uninitialized pointer is dereferenced in gpiolib_seq_stop() without checking if it is valid, which can lead to invalid pointer access. The fix involves initializing s->private to NULL before allocation and checking it before dereferencing.

Impact Analysis

The impact of this vulnerability could include kernel crashes or undefined behavior due to invalid pointer dereferencing, potentially leading to system instability or denial of service. However, specific impacts are not detailed in the provided information.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-68167. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart