CVE-2024-38659: enic: Validate length of nl attributes in enic_set_vf_port
In the Linux kernel, the following vulnerability has been resolved:
enic: Validate length of nl attributes in enic_set_vf_port
enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE
is of length PORT_PROFILE_MAX and that the nl attributes
IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX.
These attributes are validated (in the function do_setlink in rtnetlink.c)
using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE
as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and
IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation
using the policy is for the max size of the attributes and not on exact
size so the length of these attributes might be less than the sizes that
enic_set_vf_port expects. This might cause an out of bands
read access in the memcpys of the data of these
attributes in enic_set_vf_port.
Security readout for executives and security teams
Plain-English summary
A local user could abuse malformed network configuration data when the Linux Cisco enic driver configures a virtual-function port. The driver may read beyond the supplied data, potentially exposing information, corrupting limited state, or disrupting the host. Systems not using enic are unlikely to reach the vulnerable code.
Executive priority
Treat as high priority on multi-user, hosting, or virtualization systems that actively use enic and expose local access to less-trusted users. For systems without enic hardware or VF port configuration, validate non-exposure and handle through the normal kernel patch cycle.
Technical view
enic_set_vf_port assumes three netlink attributes have exact fixed lengths, while rtnetlink policy validation enforces only maximum lengths. Short IFLA_PORT_PROFILE, IFLA_PORT_INSTANCE_UUID, or IFLA_PORT_HOST_UUID values can therefore reach fixed-size memcpy operations and cause an out-of-bounds read. CVSS 3.1 is 7.3: local, low-complexity, low-privilege, no user interaction.
Likely exposure
Exposure is concentrated in Linux hosts using the enic network driver and virtual-function port configuration. The record traces affected code to Linux 2.6.35 and supplies fixes across multiple stable branches. Exact applicability requires checking the running distribution kernel because vendors may backport fixes without adopting upstream version numbers.
Exploitation context
The supplied sources provide no evidence of active exploitation, and the CVE is not listed as KEV. The supplied CVSS vector describes a local attack requiring low privileges, with no user interaction. It does not support classifying this as a network-reachable vulnerability.
Researcher notes
The central defect is an exact-length assumption crossing a validation boundary that permits shorter attributes. The stated failure is an out-of-bounds read during memcpy; the bundle does not establish a reliable exploitation primitive or observed attacks. Distribution-specific backports make commit-level verification more dependable than version-string comparison alone.
Mitigation direction
Apply the distributor kernel update containing the applicable upstream stable fix.
Prioritize shared hosts using enic, SR-IOV, or virtual-function port management.
Until updated, restrict untrusted local access and authority to change VF port configuration.
If package status is unclear, obtain CVE-specific remediation guidance from the system vendor.
Validation and detection
Inventory running kernels and determine whether the enic driver is loaded and actively used.
Check vendor advisories or package changelogs for CVE-2024-38659 or a referenced fix commit.
Identify systems where less-trusted local users can initiate VF port configuration changes.
After updating, confirm the fixed kernel is running and repeat vulnerability assessment.
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-38659 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.