In the Linux kernel, the following vulnerability has been resolved:
net: libwx: fix VF illegal register access
Register WX_CFG_PORT_ST is a PF restricted register. When a VF is
initialized, attempting to read this register triggers an illegal
register access, which lead to a system hang.
When the device is VF, the bus function ID can be obtained directly from
the PCI_FUNC(pdev->devfn).
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can hang a system when a virtual function in the libwx network driver reads a register reserved for physical functions. The business risk is mainly availability loss on affected hosts, especially where these network devices are used with virtualized functions.
Executive priority
Treat this as a targeted availability risk. Prioritize kernel maintenance for virtualization or network infrastructure hosts using the affected driver path, but avoid emergency assumptions without evidence of active exploitation.
Technical view
The libwx driver accessed WX_CFG_PORT_ST during VF initialization, but that register is PF-restricted. On VF devices, the illegal access can trigger a system hang. The fix uses the PCI function ID directly for VFs instead of reading the restricted register.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with the libwx network driver and devices initialized as VFs. The source bundle does not identify distributions, hardware models, or internet-facing exposure conditions.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not claim active exploitation or provide exploit maturity. The documented impact is a system hang during VF initialization, indicating an availability-focused failure path rather than confirmed remote compromise.
Researcher notes
Evidence is narrow but specific: a PF-only register read occurs during VF initialization and can hang the system. The source bundle lacks CVSS, CWE, distro mappings, hardware identifiers, and proof of exploitability beyond the described faulty initialization path.
Mitigation direction
Update affected Linux kernels using distro or Linux stable guidance.
Prioritize hosts using libwx network devices with VFs enabled.
Review the referenced stable commits for fixed kernel branches.
Do not assume a configuration workaround unless vendor guidance documents one.
Validation and detection
Inventory kernel versions against the CVE affected and unaffected ranges.
Identify hosts loading the libwx driver or using matching network devices.
Check whether affected hosts initialize devices as virtual functions.
Confirm patched kernels include one of the referenced stable fixes.
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-46142 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
6Source 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 28, 2026, 09:35 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.