linux — security advisory
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6 OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers. Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet. It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten. The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace. ND fields should not be accessed in non-ND packet
- Products
- linux
- Affected versions
- 6.1.27-1, 6.1.37-1, 6.1.38-1, 6.1.38-2, 6.1.38-2~bpo11+1, 6.1.38-3, 6.1.38-4, 6.1.38-4~bpo11+1, 6.1.52-1, 6.1.55-1, 6.1.55-1~bpo11+1, 6.1.64-1, 6.1.66-1, 6.1.67-1, 6.1.69-1, 6.1.69-1~bpo11+1, 6.1.76-1, 6.1.76-1~bpo11+1, 6.1.82-1, 6.1.85-1, 6.1.90-1, 6.1.90-1~bpo11+1, 6.1.94-1~bpo11+1
- Fixed versions
- 6.1.94-1, 6.8.12-1
- CVEs
- CVE-2024-38558
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 16:36 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6 OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers. Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet. It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten. The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace. ND fields should not be accessed in non-ND packet
osv:DEBIAN-CVE-2024-38558
linux
Fixed versions: 6.1.94-1
linux
Fixed versions: 6.8.12-1
linux
Fixed versions: 6.8.12-1
Complete source record
{
"id": "dd5432871fd108f7085324e4a2f0831cadaca8c0e31599a4d597c3c316dfde1e",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2024-38558",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2024-38558",
"summary": "In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6 OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers. Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet. It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten. The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace. ND fields should not be accessed in non-ND packet",
"evidence": "osv:DEBIAN-CVE-2024-38558",
"products": [
{
"name": {
"value": "linux",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.94-1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "6.1.27-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.37-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-3",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.52-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.64-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.66-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.67-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.76-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.76-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.82-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.85-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.90-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.90-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.94-1~bpo11+1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "linux",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.8.12-1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "linux",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.8.12-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2024-38558",
"aliases": [
"DEBIAN-CVE-2024-38558"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.94-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"6.1.27-1",
"6.1.37-1",
"6.1.38-1",
"6.1.38-2",
"6.1.38-2~bpo11+1",
"6.1.38-3",
"6.1.38-4",
"6.1.38-4~bpo11+1",
"6.1.52-1",
"6.1.55-1",
"6.1.55-1~bpo11+1",
"6.1.64-1",
"6.1.66-1",
"6.1.67-1",
"6.1.69-1",
"6.1.69-1~bpo11+1",
"6.1.76-1",
"6.1.76-1~bpo11+1",
"6.1.82-1",
"6.1.85-1",
"6.1.90-1",
"6.1.90-1~bpo11+1",
"6.1.94-1~bpo11+1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-38558.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.12-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-38558.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.12-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-38558.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-15T09:47:34.089081866Z",
"provider": "osv",
"upstream": [
"CVE-2024-38558"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2024-38558"
]
},
"related_cves": [
{
"value": "CVE-2024-38558",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 327724,
"published_at": "2024-06-19T14:15:15.983+00:00"
}