🛡️ CVE-2024-36930 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

spi: fix null pointer dereference within spi_sync

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

spi: fix null pointer dereference within spi_sync

If spi_sync() is called with the non-empty queue and the same spi_message

is then reused, the complete callback for the message remains set while

the context is cleared, leading to a null pointer dereference when the

callback is invoked from spi_finalize_current_message().

With function inlining disabled, the call stack might look like this:

_raw_spin_lock_irqsave from complete_with_flags+0x18/0x58

complete_with_flags from spi_complete+0x8/0xc

spi_complete from spi_finalize_current_message+0xec/0x184

spi_finalize_current_message from spi_transfer_one_message+0x2a8/0x474

spi_transfer_one_message from __spi_pump_transfer_message+0x104/0x230

__spi_pump_transfer_message from __spi_transfer_message_noqueue+0x30/0xc4

__spi_transfer_message_noqueue from __spi_sync+0x204/0x248

__spi_sync from spi_sync+0x24/0x3c

spi_sync from mcp251xfd_regmap_crc_read+0x124/0x28c [mcp251xfd]

mcp251xfd_regmap_crc_read [mcp251xfd] from _regmap_raw_read+0xf8/0x154

_regmap_raw_read from _regmap_bus_read+0x44/0x70

_regmap_bus_read from _regmap_read+0x60/0xd8

_regmap_read from regmap_read+0x3c/0x5c

regmap_read from mcp251xfd_alloc_can_err_skb+0x1c/0x54 [mcp251xfd]

mcp251xfd_alloc_can_err_skb [mcp251xfd] from mcp251xfd_irq+0x194/0xe70 [mcp251xfd]

mcp251xfd_irq [mcp251xfd] from irq_thread_fn+0x1c/0x78

irq_thread_fn from irq_thread+0x118/0x1f4

irq_thread from kthread+0xd8/0xf4

kthread from ret_from_fork+0x14/0x28

Fix this by also setting message->complete to NULL when the transfer is

complete.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-36930 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.8.10)
  • linux-kernel (from 6.7 up to 6.8.10)

Timeline and source

Published on 30 May 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-36930 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-05-30
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.8.10
linux-kernel 6.7 6.8.10

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-36930 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024