Skip to main content
EPSS 0.1%top 96%

Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix invalid pointer access in debugfs If the memory allocation in… (CVE-2025-68167)

0
Medium
Published: 12/16/2025 (12/16/2025, 14:15:00 UTC)
Source: GCVE Database
Product: linux-hwe-edge

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 v3.1

Score 7.8high

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected software

Affected versions
<6.17.0-1007.7~24.04.1<6.17.0-1008.8~24.04.1<6.17.0-1008.8<6.17.0-1011.11

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/30/2026, 18:40:31 UTC

Technical Analysis

The Linux kernel's gpiolib subsystem contained a vulnerability where failure of memory allocation in the gpiolib_seq_start() function left the s->private pointer uninitialized. Subsequent dereferencing of this pointer in gpiolib_seq_stop() without a null check could cause invalid pointer access. This flaw was fixed by initializing s->private to NULL before calling kzalloc() and adding a check before dereferencing it, preventing potential kernel crashes or other severe impacts.

Potential Impact

Successful exploitation of this vulnerability could lead to kernel crashes or other severe impacts affecting confidentiality, integrity, and availability of the system, as indicated by the CVSS vector (C:H/I:H/A:H). No known exploits are reported in the wild at this time.

Mitigation Recommendations

A fix for this vulnerability has been implemented in the Linux kernel by initializing the s->private pointer to NULL before memory allocation and checking it before dereference. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-v8v6-qqfp-9rx7
Osv Schema Version
1.4.0
Aliases
["CVE-2025-68167"]
Database Specific Severity
HIGH
Cvss Version
3.1

Threat ID: 6a6b72d39c2644c7f84782c5

Added to database: 07/30/2026, 15:50:43 UTC

Last enriched: 07/30/2026, 18:40:31 UTC

Last updated: 09/10/2026, 19:24:57 UTC

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses