CVE-2024-36930

Kernel crash via stale SPI completion callback

Published May 30, 2024 · Updated May 11, 2026

NULL pointer dereference in the Linux kernel SPI core allows local users to crash the kernel by reusing an SPI message after a queued transfer. spi_sync clears the completion context but leaves message->complete set, so spi_finalize_current_message invokes the stale callback with a null context. Reachability requires local access and an SPI caller that reuses a message after a non-empty queued transfer; the bounded impact is a kernel crash.

CVSS severity5.5
Medium
EPSS probability0.23%
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

NULL pointer dereference in the Linux kernel SPI core allows local users to crash the kernel by reusing an SPI message after a queued transfer. spi_sync clears the completion context but leaves message->complete set, so spi_finalize_current_message invokes the stale callback with a null context. Reachability requires local access and an SPI caller that reuses a message after a non-empty queued transfer; the bounded impact is a kernel crash.

The record

CVE
CVE-2024-36930
Published
May 30, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-476, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 30, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 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=6.0
  2. Affected versionversion=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <2070d008cc08bff50a58f0f4d30f12d3ebf94c00
  3. Affected versionversion=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <4756fa529b2f12b7cb8f21fe229b0f6f47190829
  4. Affected versionversion=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <a30659f1576d2c8e62e7426232bb18b885fd951a
  5. Affected versionversion=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <e005d6754e3e440257006795b687c4ad8733b493

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.0; version=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <2070d008cc08bff50a58f0f4d30f12d3ebf94c00; version=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <4756fa529b2f12b7cb8f21fe229b0f6f47190829; version=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <a30659f1576d2c8e62e7426232bb18b885fd951a; version=ae7d2346dc89ae89a6e0aabe6037591a11e593c0 <e005d6754e3e440257006795b687c4ad8733b493

Published CVSS scores

5.5UbuntuCVSS: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-476NULL Pointer Dereference
T1499.004Application or System Exploitation

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