GHSA-PP7W-23PG-4FGH
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
bpf: Disallow interpreter fallback for arena-related insns
Since the interpreter does not support the arena-related insns, interpreter fallback should not be allowed for these insns in core.c::__bpf_prog_select_runtime().
Currently, when the interpreter executes the arena ST/LDX/STX insns, it would hit the BUG_ON() in ___bpf_prog_run() at run time.
[ 2.579196] BPF interpreter: unknown opcode a2 (imm: 0x0) [ 2.579998] ------------[ cut here ]------------ [ 2.580652] kernel BUG at kernel/bpf/core.c:2349! [ 2.581314] Oops: invalid opcode: 0000 [#1] SMP PTI
Set jit_required as true when arena map is used in the prog to disallow interpreter fallback for arena-related insns.
{
"affected": [],
"aliases": [
"CVE-2026-93044"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:57Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Disallow interpreter fallback for arena-related insns\n\nSince the interpreter does not support the arena-related insns,\ninterpreter fallback should not be allowed for these insns in\ncore.c::__bpf_prog_select_runtime().\n\nCurrently, when the interpreter executes the arena ST/LDX/STX insns,\nit would hit the BUG_ON() in ___bpf_prog_run() at run time.\n\n[ 2.579196] BPF interpreter: unknown opcode a2 (imm: 0x0)\n[ 2.579998] ------------[ cut here ]------------\n[ 2.580652] kernel BUG at kernel/bpf/core.c:2349!\n[ 2.581314] Oops: invalid opcode: 0000 [#1] SMP PTI\n\nSet jit_required as true when arena map is used in the prog to disallow\ninterpreter fallback for arena-related insns.",
"id": "GHSA-pp7w-23pg-4fgh",
"modified": "2026-09-17T18:32:07Z",
"published": "2026-09-17T18:32:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93044"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/34746b5a84ec37c0ea2bf6808c65c5ed8790eb51"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/408b6d3bc19c4aa852ab7ee2f447756e52e69967"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.