CVE-2024-36945: net/smc: fix neighbour and rtable leak in smc_ib_find_route()
In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix neighbour and rtable leak in smc_ib_find_route()
In smc_ib_find_route(), the neighbour found by neigh_lookup() and rtable
resolved by ip_route_output_flow() are not released or put before return.
It may cause the refcount leak, so fix it.
Security readout for executives and security teams
Plain-English summary
A Linux kernel networking function fails to release routing and neighbour references. Repeated use may consume kernel resources and eventually disrupt service availability. The supplied assessment rates this high severity, but it provides no evidence of data theft, modification, or active exploitation.
Executive priority
Treat as a high-priority availability issue on exposed or SMC-enabled Linux systems. Establish actual fleet exposure before emergency action; prioritize supported kernel updates where affected code is present. There is no supplied evidence of active exploitation.
Technical view
The flaw is a reference-count leak in smc_ib_find_route(). Objects returned by neigh_lookup() and ip_route_output_flow() were not released before return. The kernel stable commits correct the cleanup. The supplied CVSS 3.1 score is 7.5, with availability impact only.
Likely exposure
Exposure is limited to Linux systems containing the affected SMC networking code, especially where the relevant route-discovery path is exercised. Exact distribution, appliance, and configuration exposure cannot be established from the supplied version data, which is ambiguous.
Exploitation context
The bundle marks this CVE as absent from KEV and cites no active exploitation or public exploit. Network reachability appears in the supplied CVSS vector, but the sources do not explain practical triggering conditions or demonstrate reliable remote denial of service.
Researcher notes
The affected-version representation is internally unclear, including a duplicated commit identifier and an unusual version list. Validate ancestry and backports against vendor kernels rather than relying solely on version strings. The bundle provides fixes but no triggering analysis, proof of exploitation, or confirmed attack telemetry.
Mitigation direction
Apply a vendor-supported kernel update incorporating the relevant stable fix.
Check Linux distribution and appliance advisories for corrected package versions.
Prioritize systems using SMC networking or showing unexplained resource exhaustion.
Follow NetApp guidance separately for potentially affected NetApp products.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Determine whether SMC networking is present and operationally used.
Compare installed kernels with vendor advisories and the four referenced stable commits.
After updating, confirm the running kernel is the intended corrected build.
Monitor affected systems for recurring resource exhaustion or availability degradation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36945 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.