From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80865: bpf: Add missing access_ok call to copy_user_syms
Date: Fri, 4 Sep 2026 18:46:32 +0200 [thread overview]
Message-ID: <2026090431-CVE-2026-80865-ed5a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
bpf: Add missing access_ok call to copy_user_syms
As reported by sashiko we use __get_user without prior access_ok call on the
user space pointer. Adding the missing call for the whole pointer array.
Plus removing the err check in the error path, because it's not needed and
also we can return -ENOMEM directly from the first kvmalloc_array fail path.
[1] https://lore.kernel.org/bpf/20260611115503.AC16D1F00893@smtp.kernel.org/
The Linux kernel CVE team has assigned CVE-2026-80865 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 6.1.178 with commit a67f7f9647cb243b3be32163e88e5bc76e3d51e9
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 6.6.145 with commit 8b719cef5ac30ab83ce5693c5faf10e4944874af
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 6.12.97 with commit 128391b57e0977c35243672a6f970073651f3831
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 6.18.40 with commit 0b6252afcd1965f77c6a6f8a802a2e1381822b98
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 7.1.5 with commit 28ce7bcf8a29aa395b60764df4c97be745de89d0
Issue introduced in 5.19 with commit 0236fec57a15dc2a068dfe4488e0c2ab4559b1ec and fixed in 7.2 with commit d5dc200c3a3f217de072af269dd90adddf90e48d
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-80865
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:
kernel/trace/bpf_trace.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/a67f7f9647cb243b3be32163e88e5bc76e3d51e9
https://git.kernel.org/stable/c/8b719cef5ac30ab83ce5693c5faf10e4944874af
https://git.kernel.org/stable/c/128391b57e0977c35243672a6f970073651f3831
https://git.kernel.org/stable/c/0b6252afcd1965f77c6a6f8a802a2e1381822b98
https://git.kernel.org/stable/c/28ce7bcf8a29aa395b60764df4c97be745de89d0
https://git.kernel.org/stable/c/d5dc200c3a3f217de072af269dd90adddf90e48d
reply other threads:[~2026-09-04 16:52 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=2026090431-CVE-2026-80865-ed5a@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.