CVE-2024-36945

Kernel resource exhaustion via SMC reference leak

Published May 30, 2024 · Updated Aug 5, 2026

Resource leak in Linux kernel 5.16 through 6.9-rc7 allows local users to exhaust kernel resources through SMC route lookups. The smc_ib_find_route() path returns after copying neighbour data without releasing the neighbour reference or putting the resolved IPv4 route. Repeated SMC route resolution by a low-privileged local user retains both objects until resources are exhausted; no specific hang, crash, or reboot mode has been published.

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

Resource leak in Linux kernel 5.16 through 6.9-rc7 allows local users to exhaust kernel resources through SMC route lookups. The smc_ib_find_route() path returns after copying neighbour data without releasing the neighbour reference or putting the resolved IPv4 route. Repeated SMC route resolution by a low-privileged local user retains both objects until resources are exhausted; no specific hang, crash, or reboot mode has been published.

The record

CVE
CVE-2024-36945
Published
May 30, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-401, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 30, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 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=5.16
  2. Affected versionversion=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <2ddc0dd7fec86ee53b8928a5cca5fbddd4fc7c06
  3. Affected versionversion=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <5df93c029a907b0ff5a4eeadd77ba06ff0a277d2
  4. Affected versionversion=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <d5a466ab6e78d6f2e0f64435f1e17246c8e941ff
  5. Affected versionversion=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <da91e447d06dc649fcf46e59122e7bf8f0b2e0db

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.16; version=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <2ddc0dd7fec86ee53b8928a5cca5fbddd4fc7c06; version=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <5df93c029a907b0ff5a4eeadd77ba06ff0a277d2; version=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <d5a466ab6e78d6f2e0f64435f1e17246c8e941ff; version=e5c4744cfb598f98672f8d21d59ef2c1fa9c9b5f <da91e447d06dc649fcf46e59122e7bf8f0b2e0db

Published CVSS scores

5.5NIST NVDCVSS: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 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

CWE-401Missing Release of Memory after Effective Lifetime
T1499Endpoint Denial of Service

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