From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80675: libbpf: Reject non-exclusive metadata maps in the signed loader
Date: Fri, 28 Aug 2026 08:49:52 +0200 [thread overview]
Message-ID: <2026082849-CVE-2026-80675-bef6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
libbpf: Reject non-exclusive metadata maps in the signed loader
The loader verifies map->sha against the metadata hash in its
instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is
called on the frozen map.
While the map is frozen, the /signed loader/ must also ensure the map
is exclusive, as, without exclusivity (which a hostile host could just
omit when loading the loader), another BPF program with map access can
mutate the contents afterwards, so the check passes on stale data.
With the extra check as part of the signed loader, it now refuses to
move on with map->sha validation if the host set it up wrongly.
The Linux kernel CVE team has assigned CVE-2026-80675 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and fixed in 6.18.40 with commit b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb
Issue introduced in 6.18 with commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and fixed in 7.1.5 with commit 0dad5adeb34b6f78a883e8faa6a1c947a240e7c9
Issue introduced in 6.18 with commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and fixed in 7.2 with commit 0fb6c9ed6493b4af01be8bb0a384574eba7df636
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-80675
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:
include/linux/bpf.h
kernel/bpf/syscall.c
tools/lib/bpf/gen_loader.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/b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb
https://git.kernel.org/stable/c/0dad5adeb34b6f78a883e8faa6a1c947a240e7c9
https://git.kernel.org/stable/c/0fb6c9ed6493b4af01be8bb0a384574eba7df636
reply other threads:[~2026-08-28 6: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=2026082849-CVE-2026-80675-bef6@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.