In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix CT entry update leaks of modify header context
The cited commit allocates a new modify header to replace the old
one when updating CT entry. But if failed to allocate a new one, eg.
exceed the max number firmware can support, modify header will be
an error pointer that will trigger a panic when deallocating it. And
the old modify header point is copied to old attr. When the old
attr is freed, the old modify header is lost.
Fix it by restoring the old attr to attr when failed to allocate a
new modify header context. So when the CT entry is freed, the right
modify header context will be freed. And the panic of accessing
error pointer is also fixed.
Security readout for executives and security teams
Plain-English summary
A Linux networking driver flaw can crash the kernel and leak a hardware modification-header resource when updating a connection-tracking entry fails. A crash could interrupt network services or an entire host. The supplied rating is critical, but the public description does not establish how an attacker could force the failure or obtain confidentiality or integrity impact.
Executive priority
Treat as an urgent availability risk for exposed mlx5e-based infrastructure, particularly critical network hosts. Validate applicability before emergency changes because the affected-version information is unclear. There is no supplied evidence of active exploitation, but kernel panic potential supports prompt vendor-guided patching.
Technical view
In net/mlx5e, a failed replacement modify-header allocation leaves an error pointer while copying the previous pointer into an old attribute. Cleanup can dereference the error pointer and panic; freeing the old attribute also loses the valid context. The fix restores the old attribute on allocation failure, allowing correct later cleanup.
Likely exposure
Exposure is most plausible on Linux systems using the mlx5e driver and the affected connection-tracking entry update path, especially where firmware modification-header capacity can be exhausted. The supplied affected-version data names Linux 6.3, 6.6.45, 6.10.4, and 6.11 but is ambiguous, so distribution-specific mapping is required.
Exploitation context
The supplied CVSS 3.1 vector rates this 9.8 and network-accessible without authentication or user interaction. However, the technical description only demonstrates resource leakage and a kernel panic after allocation failure. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The documented trigger is failure to allocate a replacement modify-header context, including firmware-capacity exhaustion. The resulting cleanup flaw combines an error-pointer panic with loss of the prior context. The sources do not establish attacker control, reliable remote triggering, privilege escalation, data disclosure, or data modification despite the supplied CVSS impacts.
Mitigation direction
Identify systems using the mlx5e driver and connection-tracking functionality.
Consult Linux distribution advisories to map installed kernels to the referenced fixes.
Upgrade to a vendor-supported kernel containing the applicable stable fix.
Prioritize network-critical hosts where a kernel panic would cause material disruption.
Validation and detection
Record kernel and distribution package versions on potentially exposed systems.
Confirm whether mlx5e hardware and the affected connection-tracking path are in use.
Verify the installed kernel includes the applicable referenced stable commit or vendor backport.
Review kernel logs for mlx5e failures, allocation errors, or unexplained panics.
Confirm normal resource cleanup and stability after remediation using safe operational testing.
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-43864 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.