GHSA-94HW-5J8J-HWQ4
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
riscv, bpf: Fix memory leak in bpf_jit_free
When bpf_int_jit_compile() is called for subprograms, it returns early during the first pass (!prog->is_func || extra_pass is false), keeping ctx->offset alive for the subsequent extra pass.
If JIT compilation fails for a later subprogram, the BPF core aborts and calls bpf_jit_free() to clean up the first subprogram. However, bpf_jit_free() fails to free jit_data->ctx.offset, which causes a memory leak of the JIT context offsets array.
Fix this by adding the missing kfree(jit_data->ctx.offset) in bpf_jit_free().
{
"affected": [],
"aliases": [
"CVE-2026-92519"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:54Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv, bpf: Fix memory leak in bpf_jit_free\n\nWhen bpf_int_jit_compile() is called for subprograms, it returns early\nduring the first pass (!prog-\u003eis_func || extra_pass is false), keeping\nctx-\u003eoffset alive for the subsequent extra pass.\n\nIf JIT compilation fails for a later subprogram, the BPF core aborts\nand calls bpf_jit_free() to clean up the first subprogram. However,\nbpf_jit_free() fails to free jit_data-\u003ectx.offset, which causes a\nmemory leak of the JIT context offsets array.\n\nFix this by adding the missing kfree(jit_data-\u003ectx.offset) in\nbpf_jit_free().",
"id": "GHSA-94hw-5j8j-hwq4",
"modified": "2026-09-17T18:32:07Z",
"published": "2026-09-17T18:32:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-92519"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2a3a29e90021806ea00527f6458cfd2edb58b42a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/369e4635d04801f394d5bd42556f21029e95ff93"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5cadc66b534fe8140441916200a20c7efb06a388"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b594c23f584ab032a5eae809eee81b809dd27330"
}
],
"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.