In the Linux kernel, the following vulnerability has been resolved:
nfp: flower: handle acti_netdevs allocation failure
The kmalloc_array() in nfp_fl_lag_do_work() will return null, if
the physical memory has run out. As a result, if we dereference
the acti_netdevs, the null pointer dereference bugs will happen.
This patch adds a check to judge whether allocation failure occurs.
If it happens, the delayed work will be rescheduled and try again.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability flaw in the nfp flower networking driver. If memory allocation fails in a specific delayed work path, the kernel can dereference a null pointer. The available sources point to a crash or denial-of-service risk, not data theft or remote code execution.
Executive priority
Treat as a targeted kernel availability issue. Patch during normal Linux kernel maintenance, faster for infrastructure using Netronome/NFP networking features or systems where kernel crashes would create service-impacting outages.
Technical view
CVE-2024-27046 fixes missing error handling after kmalloc_array() in nfp_fl_lag_do_work(). When allocation of acti_netdevs fails, later dereference can cause a null pointer dereference. The fix checks allocation failure and reschedules delayed work to retry.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the nfp flower driver code path relevant to LAG handling. The source bundle lists affected Linux kernel lines including 4.18 and multiple stable branches through 6.9, with default status affected for listed releases.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, or exploit details. The condition depends on allocation failure, so practical impact is most clearly local system instability or kernel crash under relevant driver and memory-pressure conditions.
Researcher notes
The evidence supports a missing allocation-failure check, not a broad remotely exploitable flaw. No CVSS, CWE, or KEV signal is provided. Validate exposure by mapping kernel backports and actual nfp flower/LAG feature use rather than relying only on upstream version numbers.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Prioritize systems using the nfp flower driver or related LAG offload paths.
Check Debian LTS advisories if running affected Debian-based kernels.
If no vendor package is available, track vendor kernel guidance.
Plan reboot or live-patch procedures according to kernel update policy.
Validation and detection
Inventory running kernel versions against the affected version list.
Confirm whether nfp flower driver functionality is present or loaded.
Verify the vendor kernel includes a backport for CVE-2024-27046.
Review kernel logs for nfp_fl_lag_do_work null dereference crashes.
Confirm patched systems boot the expected updated kernel.
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-27046 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.