CVE-2026-97495Hinoki check available

Kernel memory corruption via unchecked doorbell ID

Published Sep 24, 2026 · Updated Sep 24, 2026

Out-of-bounds write in Linux before 6.12.111 or 6.18.53 allows local users to corrupt kernel memory through CRIU queue restore. allocate_doorbell passes an unbounded userspace restore_id to __test_and_set_bit, which writes past the fixed-size doorbell_bitmap when the ID reaches the queue limit. Reaching this path requires the AMD KFD CRIU restore ioctl, administrative checkpoint-restore capability, and a supported AMD GPU; the bounded consequence is a kernel crash or memory corruption.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Out-of-bounds write in Linux before 6.12.111 or 6.18.53 allows local users to corrupt kernel memory through CRIU queue restore. allocate_doorbell passes an unbounded userspace restore_id to __test_and_set_bit, which writes past the fixed-size doorbell_bitmap when the ID reaches the queue limit. Reaching this path requires the AMD KFD CRIU restore ioctl, administrative checkpoint-restore capability, and a supported AMD GPU; the bounded consequence is a kernel crash or memory corruption.

The record

CVE
CVE-2026-97495
Published
Sep 24, 2026
Updated
Sep 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Sep 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 24, 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=0 <6.12.111
  2. Affected versionversion=0 <6.18.53
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1f087bb8cf9e8797633da35c85435e557ef74d06
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c2c89118c27cbd3adace62c5df19d15b0e96ade1
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0cecd04a4fc4c75e375b91cf53eab5ba2e4ab7f

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.12.111; version=0 <6.18.53; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1f087bb8cf9e8797633da35c85435e557ef74d06; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c2c89118c27cbd3adace62c5df19d15b0e96ade1; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0cecd04a4fc4c75e375b91cf53eab5ba2e4ab7f

Published CVSS scores

No CVSS assessment is available in this record.

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.

Activity data is delayed. The latest report is Sep 28, 2026.

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

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
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

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started