[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121627-CVE-2025-68167-a6eb@gregkh>
Date: Tue, 16 Dec 2025 14:43:28 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68167: gpiolib: fix invalid pointer access in debugfs
From: Greg Kroah-Hartman <gregkh@...nel.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.
The Linux kernel CVE team has assigned CVE-2025-68167 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit e348544f7994d252427ed3ae637c7081cbb90f66 and fixed in 6.12.58 with commit 70180a6031056096c93ed2f47c41803268bdd91c
Issue introduced in 6.9 with commit e348544f7994d252427ed3ae637c7081cbb90f66 and fixed in 6.17.8 with commit 3c91c8f424d3e44c8645ab765a38773e58afb07d
Issue introduced in 6.9 with commit e348544f7994d252427ed3ae637c7081cbb90f66 and fixed in 6.18 with commit 2f6115ad8864cf3f48598f26c74c7c8e5c391919
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-68167
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpio/gpiolib.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/70180a6031056096c93ed2f47c41803268bdd91c
https://git.kernel.org/stable/c/3c91c8f424d3e44c8645ab765a38773e58afb07d
https://git.kernel.org/stable/c/2f6115ad8864cf3f48598f26c74c7c8e5c391919
Powered by blists - more mailing lists