libbpf: Use OPTS_SET() macro in bpf_xdp_query()
In the Linux kernel, the following vulnerability has been resolved: libbpf: Use OPTS_SET() macro in bpf_xdp_query() When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds. The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.6.23, 6.7.11, 6.8.2
- CVEs
- CVE-2024-27050
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:50 UTC · Revision 1
Source evidence
libbpf: Use OPTS_SET() macro in bpf_xdp_query()
core-osv · Original sourcePublished 1 May 2024, 12:54 UTC
In the Linux kernel, the following vulnerability has been resolved: libbpf: Use OPTS_SET() macro in bpf_xdp_query() When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds. The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.
osv:CVE-2024-27050
Kernel
Fixed versions: 6.6.23, 6.7.11, 6.8.2
Complete source record
{
"id": "82eef3012f0d132c7c0a950036f3d70edffd5af77d1c120c5099f1b9d5efa12d",
"url": "https://osv.dev/vulnerability/CVE-2024-27050",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "libbpf: Use OPTS_SET() macro in bpf_xdp_query()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: libbpf: Use OPTS_SET() macro in bpf_xdp_query() When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds. The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.",
"evidence": "osv:CVE-2024-27050",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.23",
"evidence": "/affected/1/ranges"
},
{
"value": "6.7.11",
"evidence": "/affected/1/ranges"
},
{
"value": "6.8.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-27050",
"aliases": [
"CVE-2024-27050"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "13ce2daa259a3bfbc9a5aeeee8b9a87058703731"
},
{
"fixed": "fa5bef5e80c6a3321b2b1a7070436f3bc5daf07c"
},
{
"fixed": "682ddd62abd4bdcee7584246903e7a2df005fe0d"
},
{
"fixed": "cd3be9843247edb8fc6fcd8d8237cbce2bc19f5e"
},
{
"fixed": "92a871ab9fa59a74d013bc04f321026a057618e7"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-27050.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.6.0"
},
{
"fixed": "6.6.23"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.7.11"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.8.0"
},
{
"fixed": "6.8.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-27050.json"
}
}
],
"modified": "2026-10-28T02:30:38.232658359Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/682ddd62abd4bdcee7584246903e7a2df005fe0d",
"https://git.kernel.org/stable/c/92a871ab9fa59a74d013bc04f321026a057618e7",
"https://git.kernel.org/stable/c/cd3be9843247edb8fc6fcd8d8237cbce2bc19f5e",
"https://git.kernel.org/stable/c/fa5bef5e80c6a3321b2b1a7070436f3bc5daf07c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/27xxx/CVE-2024-27050.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-27050",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/27xxx/CVE-2024-27050.json"
}
},
"related_cves": [
{
"value": "CVE-2024-27050",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505486,
"published_at": "2024-05-01T12:54:35.555+00:00"
}