gpiolib: fix invalid pointer access in debugfs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.586.17.86.18In 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.
From the CVE record · Linux
The Linux kernel's gpiolib debugfs code can dereference an uninitialized pointer if memory allocation in gpiolib_seq_start() fails. This can cause invalid pointer access; the input does not establish how an attacker could trigger the condition or whether access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.