From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-92519: riscv, bpf: Fix memory leak in bpf_jit_free
Date: Thu, 17 Sep 2026 17:15:09 +0100 [thread overview]
Message-ID: <2026091730-CVE-2026-92519-2f2e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In 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().
The Linux kernel CVE team has assigned CVE-2026-92519 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 48a8f78c50bd6f7f08fd40daa62252fd043f2f18 and fixed in 6.12.110 with commit b594c23f584ab032a5eae809eee81b809dd27330
Issue introduced in 6.6 with commit 48a8f78c50bd6f7f08fd40daa62252fd043f2f18 and fixed in 6.18.52 with commit 5cadc66b534fe8140441916200a20c7efb06a388
Issue introduced in 6.6 with commit 48a8f78c50bd6f7f08fd40daa62252fd043f2f18 and fixed in 7.2.6 with commit 2a3a29e90021806ea00527f6458cfd2edb58b42a
Issue introduced in 6.6 with commit 48a8f78c50bd6f7f08fd40daa62252fd043f2f18 and fixed in 7.3-rc1 with commit 369e4635d04801f394d5bd42556f21029e95ff93
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-92519
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/riscv/net/bpf_jit_core.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b594c23f584ab032a5eae809eee81b809dd27330
https://git.kernel.org/stable/c/5cadc66b534fe8140441916200a20c7efb06a388
https://git.kernel.org/stable/c/2a3a29e90021806ea00527f6458cfd2edb58b42a
https://git.kernel.org/stable/c/369e4635d04801f394d5bd42556f21029e95ff93
reply other threads:[~2026-09-17 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091730-CVE-2026-92519-2f2e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.