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() fail…

Code

The project this record applies to. Exploit listings stay in References.

• Repository · git.kernel.org
• Repository · git.kernel.org
• Repository · git.kernel.org

Timeline

Detection, updates, and resolution for this record.

1. Dec 16, 2025 · NIST NVD

   Detected

   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.

2. Oct 14, 2026 · NIST NVD

   Updated

   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.

Sources

• CVE.orgVulnerability recordCVE-2025-68167

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2025-68167

  30-day exploitation probability 0.2%

  first.org
• NIST NVDVulnerability recordCVE-2025-68167

  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().

  nvd.nist.gov

References

• Reference · git.kernel.org
• Reference · git.kernel.org
• Reference · git.kernel.org