CVE-2024-26734: devlink: fix possible use-after-free and memory leaks in devlink_init()
In the Linux kernel, the following vulnerability has been resolved:
devlink: fix possible use-after-free and memory leaks in devlink_init()
The pernet operations structure for the subsystem must be registered
before registering the generic netlink family.
Make an unregister in case of unsuccessful registration.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux devlink initialization can leave kernel networking resources in an unsafe state, creating possible use-after-free and memory-leak conditions. A successful attack could compromise confidentiality, integrity, and availability, but the supplied CVSS assessment requires local access, low privileges, and high attack complexity.
Executive priority
Treat as a high-priority kernel maintenance issue rather than an internet-wide emergency. Schedule prompt remediation on exposed multi-user or shared-compute systems. Accelerate action where untrusted users have local accounts or workloads, while following vendor guidance because the available evidence does not establish remote or active exploitation.
Technical view
devlink_init() registered its generic netlink family before the subsystem’s per-network-namespace operations. The corrected design registers pernet operations first and unregisters them if later registration fails. This addresses possible use-after-free and memory leaks during initialization or failed setup.
Likely exposure
The source bundle identifies Linux versions 6.3, 6.6.19, 6.7.7, and 6.8 as affected. Distribution kernels may carry backported fixes despite their displayed version, so exposure cannot be determined from version numbers alone. Systems where untrusted local users can run code deserve closer attention.
Exploitation context
The CVSS vector describes a local, high-complexity attack requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle states this CVE is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The security issue concerns initialization and error-path lifetime management, not an identified remote packet-processing flaw. Three stable-kernel commits are supplied, likely reflecting fixes for different maintained branches. The bundle does not map each commit to a specific version or provide exploitability prerequisites beyond the CVSS vector.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable stable fix.
Check distribution security advisories for backported fixes before relying on kernel version strings.
Prioritize multi-user systems and hosts permitting untrusted local code execution.
Use normal change controls and reboot requirements specified by the kernel vendor.
Validation and detection
Inventory running kernel versions across Linux hosts.
Confirm package changelogs or vendor advisories explicitly reference CVE-2024-26734 or its fix.
Verify the applicable stable fix is present in custom-built kernels.
After updating, confirm hosts are running the corrected kernel, not merely storing it.
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-26734 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.