CVE-2026-23257: net: liquidio: Fix off-by-one error in PF setup_nic_devices() cleanup
In the Linux kernel, the following vulnerability has been resolved:
net: liquidio: Fix off-by-one error in PF setup_nic_devices() cleanup
In setup_nic_devices(), the initialization loop jumps to the label
setup_nic_dev_free on failure. The current cleanup loop while(i--)
skip the failing index i, causing a memory leak.
Fix this by changing the loop to iterate from the current index i
down to 0.
Also, decrement i in the devlink_alloc failure path to point to the
last successfully allocated index.
Compile tested only. Issue found using code review.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23257 is a Linux kernel bug in the LiquidIO network driver cleanup path. When device setup fails, one failed allocation index can be skipped during cleanup, causing a memory leak. The available sources do not show active exploitation, CVSS severity, or broad business impact.
Executive priority
Treat this as a routine kernel maintenance item unless LiquidIO hardware is present in critical systems. There is no source-backed evidence of active exploitation or severe impact, but patch through normal Linux update processes.
Technical view
The issue is an off-by-one error in setup_nic_devices() for the liquidio PF driver. On initialization failure, cleanup using while(i--) skips the current failing index. The fix changes cleanup to include the current index and adjusts a devlink_alloc failure path index. The patch was compile-tested only and found by code review.
Likely exposure
Exposure appears limited to Linux systems using the LiquidIO kernel driver, likely with compatible LiquidIO network hardware. The source bundle lists Linux as affected but does not provide distro package status or a precise exploitability assessment.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The bug is described as a memory leak during failed NIC setup cleanup, not as a proven remote compromise path.
Researcher notes
Evidence is narrow: Linux kernel record, stable commit references, no CVSS, no CWE, no exploit report. The upstream note says compile-tested only and found through code review, so validate downstream patch integration carefully.
Mitigation direction
Check vendor or distribution advisories for fixed kernel packages.
Prioritize Linux hosts using LiquidIO network adapters or the liquidio driver.
Apply kernel updates containing the referenced stable fixes when available.
Track distro backports because kernel commit status may differ from package versions.
Validation and detection
Confirm whether affected systems load or build the LiquidIO driver.
Compare running kernel packages against vendor advisories for this CVE.
Verify patched kernels include one of the referenced stable commits.
Record systems without LiquidIO hardware as lower exposure, not automatically remediated.
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-23257 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
8Source 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.
Mar 18, 2026, 17:41 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.