GHSA-75WF-HF48-GMFV
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
ipv6: do not let ipv6_find_hdr() return an offset past the packet end
ipv6_find_hdr() walks the extension header chain, skipping each header by the length that header itself declares. ipv6_optlen() returns up to 2048, and the skip is never checked against skb->len, so the offset stored in *offset can point past the end of the packet.
openvswitch installs that offset as the transport header, and update_ipv6_checksum() then reads and writes the transport checksum field out of bounds:
BUG: KASAN: slab-use-after-free in inet_proto_csum_replace16+0x445/0x470 Read of size 2 at addr ffff88810b754b06 by task ovs_ipv6_oob/629 CPU: 4 UID: 1000 PID: 629 Comm: ovs_ipv6_oob Tainted: G N 7.3.0-rc3+ #348 Call Trace: inet_proto_csum_replace16+0x445/0x470 set_ipv6_addr+0x3dd/0x460 do_execute_actions+0x6a3d/0x7c40 ovs_execute_actions+0xfd/0x480 ovs_packet_cmd_execute+0xc38/0xf20 genl_rcv_msg+0x59e/0x870 netlink_rcv_skb+0x18b/0x450 genl_rcv+0x2d/0x40 netlink_unicast+0x6bc/0xa20
The buggy address belongs to the object at ffff88810b754980 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 390 bytes inside of freed 704-byte region [ffff88810b754980, ffff88810b754c40)
Other callers use that offset too, so bound it here rather than in one caller.
Reject a header whose declared length does not fit in the packet. ipv6_find_hdr() already fails with -EBADMSG on a malformed chain, so this adds no new failure mode.
{
"affected": [],
"aliases": [
"CVE-2026-98532"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:04Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: do not let ipv6_find_hdr() return an offset past the packet end\n\nipv6_find_hdr() walks the extension header chain, skipping each header by\nthe length that header itself declares. ipv6_optlen() returns up to 2048,\nand the skip is never checked against skb-\u003elen, so the offset stored in\n*offset can point past the end of the packet.\n\nopenvswitch installs that offset as the transport header, and\nupdate_ipv6_checksum() then reads and writes the transport checksum field\nout of bounds:\n\n BUG: KASAN: slab-use-after-free in inet_proto_csum_replace16+0x445/0x470\n Read of size 2 at addr ffff88810b754b06 by task ovs_ipv6_oob/629\n CPU: 4 UID: 1000 PID: 629 Comm: ovs_ipv6_oob Tainted: G N 7.3.0-rc3+ #348\n Call Trace:\n inet_proto_csum_replace16+0x445/0x470\n set_ipv6_addr+0x3dd/0x460\n do_execute_actions+0x6a3d/0x7c40\n ovs_execute_actions+0xfd/0x480\n ovs_packet_cmd_execute+0xc38/0xf20\n genl_rcv_msg+0x59e/0x870\n netlink_rcv_skb+0x18b/0x450\n genl_rcv+0x2d/0x40\n netlink_unicast+0x6bc/0xa20\n\n The buggy address belongs to the object at ffff88810b754980\n which belongs to the cache skbuff_small_head of size 704\n The buggy address is located 390 bytes inside of\n freed 704-byte region [ffff88810b754980, ffff88810b754c40)\n\nOther callers use that offset too, so bound it here rather than in one\ncaller.\n\nReject a header whose declared length does not fit in the packet.\nipv6_find_hdr() already fails with -EBADMSG on a malformed chain, so this\nadds no new failure mode.",
"id": "GHSA-75wf-hf48-gmfv",
"modified": "2026-10-18T18:31:52Z",
"published": "2026-10-18T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98532"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1c70275ca87e769e1a52abc644d61372d8c016cb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1d42828565889632068fbc2983c34d57c66af4e0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4254d5878c320c19961dd0b8e1d0aca4800d8b7d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/531255de8971c06d5d5986f85fdc2525d707ba71"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/543354c6efb27eae3372a3a9674aeaa2a86e2b2c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ca96b38730e31357ef4a9d76af1336958ac670d7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dc92cb972e86790b8078337ec41015b748b8f8e5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee319bd3a0e976af5087cbe59ebc50a66f31d202"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.