CVE-2026-31772

Local kernel memory corruption via oversized BIS copy

Published May 1, 2026 · Updated May 1, 2026

Stack buffer overflow in Linux Kernel 6.13 and affected Git revisions allows local users to corrupt kernel memory through an ISO socket. The hci_le_big_create_sync function allocates space for 17 BIS entries, then memcpy copies as many as 31 conn->bis entries into that stack object. A low-privileged process must bind an ISO socket with 18 through 31 BIS entries and call listen(); the overwrite can crash the kernel or corrupt adjacent stack state.

CVSS severity7.8
High
EPSS probability0.14%
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

Stack buffer overflow in Linux Kernel 6.13 and affected Git revisions allows local users to corrupt kernel memory through an ISO socket. The hci_le_big_create_sync function allocates space for 17 BIS entries, then memcpy copies as many as 31 conn->bis entries into that stack object. A low-privileged process must bind an ISO socket with 18 through 31 BIS entries and call listen(); the overwrite can crash the kernel or corrupt adjacent stack state.

The record

CVE
CVE-2026-31772
Published
May 1, 2026
Updated
May 1, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
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=42ecf1947135110ea08abeaca39741636f9a2285 <aba0aea354015794e8312dd7efe726967e58aefe
  2. Affected versionversion=42ecf1947135110ea08abeaca39741636f9a2285 <bc39a094730ce062fa034a529c93147c096cb488
  3. Affected versionversion=42ecf1947135110ea08abeaca39741636f9a2285 <eaf32002ca7b1ba51c9f140991fd9febe6de79f0
  4. Affected versionversion=6.13
  5. Affected versionversion=8958e1cee4e2eac1a5b825caa4dd96ce9ed975dd
  6. Affected versionversion=91d19383b7ed035e22165ae5c836e50bb9f95fbe <f5d446624345d309e7a4a1b27ea9f028d6a8c5d9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=42ecf1947135110ea08abeaca39741636f9a2285 <aba0aea354015794e8312dd7efe726967e58aefe; version=42ecf1947135110ea08abeaca39741636f9a2285 <bc39a094730ce062fa034a529c93147c096cb488; version=42ecf1947135110ea08abeaca39741636f9a2285 <eaf32002ca7b1ba51c9f140991fd9febe6de79f0; version=6.13; version=8958e1cee4e2eac1a5b825caa4dd96ce9ed975dd; version=91d19383b7ed035e22165ae5c836e50bb9f95fbe <f5d446624345d309e7a4a1b27ea9f028d6a8c5d9

Published CVSS scores

7.8kernel.orgCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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