CVE-2026-68476: ipvs: reload ip header after head reallocation
In the Linux kernel, the following vulnerability has been resolved:
ipvs: reload ip header after head reallocation
__ip_vs_get_out_rt() calls skb_ensure_writable() which may
reallocate skb->head.
Security readout for executives and security teams
Plain-English summary
A Linux IPVS networking flaw occurs when packet memory may be reallocated but code retains an IP-header reference that needs reloading. The record rates it 9.8, implying possible remote, unauthenticated, no-click impact. However, the bundle documents neither a demonstrated exploit nor the exact failure outcome, so practical risk depends on affected kernel code and IPVS use.
Executive priority
Treat this as an urgent, scope-first kernel remediation issue because the assigned score is critical and the stated attack vector is remote without authentication. Identify IPVS-dependent, untrusted-network-facing systems first, then promptly patch confirmed affected builds. Avoid declaring fleet-wide exposure until vendor package mapping resolves the ambiguous version list.
Technical view
__ip_vs_get_out_rt() invokes skb_ensure_writable(), which may reallocate skb->head. The fix reloads the IP-header reference afterward, implying the prior pointer could become stale. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. No CWE, trigger details, or proven impact mechanism are supplied.
Likely exposure
Potentially exposed assets are Linux systems running affected kernel code where IPVS processes relevant traffic. The record lists affected entries from 4.10 through 7.2, including several stable-series versions, but does not define a clean version range. Confirm exposure through distribution package mapping or commit ancestry; do not rely on version-string comparison alone.
Exploitation context
The supplied record is not in KEV and provides no cited evidence of active exploitation or a public proof of concept. That does not establish absence of exploitation. The CVSS vector describes a network-reachable, low-complexity, unauthenticated, no-interaction scenario, but the bundle omits prerequisites and trigger details.
Researcher notes
The issue appears to involve an IP-header pointer becoming stale after skb head reallocation; this is inferred from the fix description. Eight stable references suggest fixes across multiple kernel branches. The bundle provides no CWE, reproducer, crash trace, exploitability analysis, or precise vulnerable commit range. Treat the CVSS impact claims as record metadata pending deeper vendor detail.
Mitigation direction
Apply vendor-supported kernel updates containing the applicable cited stable fix.
Prioritize IPVS hosts reachable from the Internet or untrusted networks.
If updates are unavailable, obtain distribution guidance; the bundle specifies no alternative mitigation.
Use normal kernel rollout controls and ensure systems boot the updated kernel.
Validation and detection
Inventory Linux systems where IPVS is enabled or actively used.
Record running kernel builds and map them to distribution advisories or cited commits.
Verify the running kernel, not merely installed packages, contains the applicable fix.
Monitor vendor advisories for clarified affected ranges and impact details.
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-68476 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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
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.