— Unscored

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: validate transport header presence in setipv6addr…

CVE-2026-99088

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: validate transport header presence in setipv6addr When executing IPv6 address rewrite actions on IPv6 fragments, setipv6addr() calls updateipv6checksum(). If parseipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDRFRAGMENT and returns early without calling skbsettransportheader(). updateipv6checksum() unconditionally evaluates skbtransportoffset() on entry before checking l4proto. Because skb->transportheader is uninitialized, this triggers a warning under CONFIGDEBUGNET=y although it is completely harmless. Fix this by returning early in updateipv6checksum() if l4proto is NEXTHDRFRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing. See the syzbot trace: !skbtransportheaderwasset(skb) WARNING: ./include/linux/skbuff.h:3075 at skbtransportheader include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skbtransportoffset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635…

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 26 October 2026
Last updated: 30 October 2026
Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 6 + 6? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99088