CVE-2026-45930: net: mctp: ensure our nlmsg responses are initialised
In the Linux kernel, the following vulnerability has been resolved:
net: mctp: ensure our nlmsg responses are initialised
Syed Faraz Abrar (@farazsth98) from Zellic, and Pumpkin (@u1f383) from
DEVCORE Research Team working with Trend Micro Zero Day Initiative
report that a RTM_GETNEIGH will return uninitalised data in the pad
bytes of the ndmsg data.
Ensure we're initialising the netlink data to zero, in the link, addr
and neigh response messages.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can expose small amounts of uninitialized kernel data through MCTP netlink neighbor responses. It is an information-disclosure concern, not described as remote compromise or code execution in the supplied sources. Business urgency depends on whether affected Linux kernels and MCTP functionality are present.
Executive priority
Track and patch through normal kernel update processes, with higher priority for shared infrastructure where small kernel memory disclosures carry greater risk. Do not treat this as confirmed active exploitation based on the supplied evidence.
Technical view
RTM_GETNEIGH responses for Linux MCTP could return uninitialized pad bytes in ndmsg data. The kernel fix zero-initializes netlink response data for link, address, and neighbor messages. Supplied records list affected Linux kernel versions and stable-tree fixes, but provide no CVSS, CWE, or exploit details.
Likely exposure
Likely exposure is Linux systems running affected kernel builds with MCTP netlink paths reachable by user-space callers. The sources do not establish remote network exposure. Version data in the bundle is incomplete and should be verified against distribution kernel advisories and stable commits.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source claims active exploitation or public weaponization. The documented behavior is unintended data disclosure through response padding, with no supplied evidence of privilege escalation or code execution.
Researcher notes
The core issue is uninitialized padding returned in MCTP netlink messages. Focus validation on affected kernel branches and whether the stable fixes are present. Evidence is limited to the CVE description and kernel stable references; impact boundaries are not fully documented.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution vendor advisories for backported patches.
Prioritize shared, multi-user, container-host, and security-sensitive Linux systems.
If patching is delayed, review vendor guidance for MCTP-specific exposure reduction.
Validation and detection
Inventory Linux kernel versions across affected fleets.
Compare installed kernels against vendor-fixed builds or referenced stable commits.
Confirm whether MCTP support is enabled or used.
Review security monitoring for unusual local netlink neighbor queries where available.
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-2026-45930 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:17 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.