Menu

Star on GitHub · 3.2k

CVE-2026-31769

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: gpib: fix use-after-free in IO ioctl handlers The IBRD, IBWRT, IBCMD, and IBWAIT ioctl handlers use a gpib_descriptor pointer a…

Published May 1, 2026CWE-416EPSS 0.18%

Overview

CVE-2026-31769 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

gpib: fix use-after-free in IO ioctl handlers

The IBRD, IBWRT, IBCMD, and IBWAIT ioctl handlers use a gpib_descriptor

pointer after board->big_gpib_mutex has been released. A concurrent

IBCLOSEDEV ioctl can free the descriptor via close_dev_ioctl() during

this window, causing a use-after-free.

The IO handlers (read_ioctl, write_ioctl, command_ioctl) explicitly

release big_gpib_mutex before calling their handler. wait_ioctl() is

called with big_gpib_mutex held, but ibwait() releases it internally

when wait_mask is non-zero. In all four cases, the descriptor pointer

obtained from handle_to_descriptor() becomes unprotected.

Fix this by introducing a kernel-only descriptor_busy reference count

in struct gpib_descriptor. Each handler atomically increments

descriptor_busy under file_priv->descriptors_mutex before releasing the

lock, and decrements it when done. close_dev_ioctl() checks

descriptor_busy under the same

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-31769?

CVE-2026-31769 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31769?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31769?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31769?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31769 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all