CVE-2026-31745

Kernel memory corruption via double-freed auxiliary device

Published May 1, 2026 · Updated May 1, 2026

Double free in the GPIO reset subsystem in Linux Kernel 6.19 through 6.19.11 allows local users to corrupt kernel memory. When __auxiliary_device_add() fails, reset_add_gpio_aux_device() calls auxiliary_device_uninit(), whose release callback frees adev, and then the error path passes the same allocation to kfree(). Reachability requires the GPIO reset auxiliary-device path and a registration failure; the public record does not describe how a low-privileged user can induce that failure or a demonstrated result beyond memory corruption.

CVSS severity7.8
High
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Double free in the GPIO reset subsystem in Linux Kernel 6.19 through 6.19.11 allows local users to corrupt kernel memory. When __auxiliary_device_add() fails, reset_add_gpio_aux_device() calls auxiliary_device_uninit(), whose release callback frees adev, and then the error path passes the same allocation to kfree(). Reachability requires the GPIO reset auxiliary-device path and a registration failure; the public record does not describe how a low-privileged user can induce that failure or a demonstrated result beyond memory corruption.

The record

CVE
CVE-2026-31745
Published
May 1, 2026
Updated
May 1, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-415
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 1, 2026CVE publishedPublication date reported by the CVE source.
  2. May 1, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5fc4e4cf7a2268b5f73700fd1e8d02159f2417d8 <1de465753220deb41569cf2add87bbb0673731db
  2. Affected versionversion=5fc4e4cf7a2268b5f73700fd1e8d02159f2417d8 <fbffb8c7c7bb4d38e9f65e0bee446685011de5d8
  3. Affected versionversion=6.19

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=5fc4e4cf7a2268b5f73700fd1e8d02159f2417d8 <1de465753220deb41569cf2add87bbb0673731db; version=5fc4e4cf7a2268b5f73700fd1e8d02159f2417d8 <fbffb8c7c7bb4d38e9f65e0bee446685011de5d8; version=6.19

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5SUSECVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-415Double Free

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo