Description
In the Linux kernel, the following vulnerability has been resolved:

bpf: Reject untrusted allocated-object pointers

When the final RCU read-side critical section ends, a local kptr is demoted
to PTR_UNTRUSTED but retains MEM_ALLOC. The pointer may be NULL or may refer
to an object whose lifetime is no longer protected.

type_is_ptr_alloc_obj() nevertheless recognizes any PTR_TO_BTF_ID with
MEM_ALLOC as a live allocated object. In particular, a refcount-only local
kptr never carries NON_OWN_REF, so it still passes the
bpf_refcount_acquire() argument check after RCU protection ends. The kfunc
can then dereference NULL or stale memory.

Make type_is_ptr_alloc_obj() reject PTR_UNTRUSTED pointers. Since
type_is_non_owning_ref() is based on the same predicate, graph kfunc
arguments obey the same live-object requirement. Fault-protected reads of
the demoted pointer remain valid: writes are already rejected, and read
fixups use bpf_may_fault_on_deref() rather than this predicate.

[ kkd: Rewrote commit log ]
Published: 2026-09-25
Score: n/a
EPSS: n/a
KEV: No
Impact: Privilege Escalation
Action: Immediate Patch
AI Analysis

Impact

The vulnerability resides in the Linux kernel’s BPF subsystem. During the end of an RCU read‑side critical section a kernel pointer (kptr) that should be treated as untrusted is still considered a live allocated object. The type_is_ptr_alloc_obj() function therefore allows the pointer to satisfy the bpf_refcount_acquire() checks, even when it is NULL or points to memory that has already been freed. Consequently a BPF helper (kfunc) can dereference a stale or null pointer, causing kernel memory corruption, which can be leveraged to gain elevated privileges or crash the system.

Affected Systems

All supported Linux kernel releases that contain the unpatched logic are affected. The issue was resolved in the upstream repository in a commit referenced in the advisory, and the kernel version that introduced the fix is after commit 6b1f786ad85a0b63393b76f5e634deab1a73198c. Administrators should verify that their distribution’s kernel, or any custom kernel they compile, incorporates this patch. No particular distribution or version was singled out in the advisory, so the default recommendation is to apply the latest kernel update from the vendor.

Risk and Exploitability

The vulnerability has a severe effect on confidentiality, integrity, and availability because it leads to memory corruption in kernel mode. Although publicly available exploit code is not yet reported, the lack of a critical‑threshold EPSS score and absence from the KEV catalog suggest the risk is not yet widely exploited, yet the attack vector is local and requires the ability to inject a malicious BPF program, which is often granted to privileged users or applications. The potential for privilege escalation makes this a high‑severity CVE, and the kernel community considers it a critical issue.

Generated by OpenCVE AI on September 25, 2026 at 15:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that contains the patch identified by commit 092c2874dc1b2060fa77a465a971acd4fdf87683 or later.
  • Verify the patch by checking the kernel source for the change that introduced the "Reject untrusted allocated‑object pointers" logic.
  • If the system must run untrusted eBPF programs, consider restricting BPF capabilities via seccomp‑bpf or putting the network namespaces into a restricted mode, or disable the specific helper if not needed.
  • Monitor kernel logs for any BPF‑related panic or crash messages that could indicate an attempted exploitation and investigate accordingly.

Generated by OpenCVE AI on September 25, 2026 at 15:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-476

Fri, 25 Sep 2026 10:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: bpf: Reject untrusted allocated-object pointers When the final RCU read-side critical section ends, a local kptr is demoted to PTR_UNTRUSTED but retains MEM_ALLOC. The pointer may be NULL or may refer to an object whose lifetime is no longer protected. type_is_ptr_alloc_obj() nevertheless recognizes any PTR_TO_BTF_ID with MEM_ALLOC as a live allocated object. In particular, a refcount-only local kptr never carries NON_OWN_REF, so it still passes the bpf_refcount_acquire() argument check after RCU protection ends. The kfunc can then dereference NULL or stale memory. Make type_is_ptr_alloc_obj() reject PTR_UNTRUSTED pointers. Since type_is_non_owning_ref() is based on the same predicate, graph kfunc arguments obey the same live-object requirement. Fault-protected reads of the demoted pointer remain valid: writes are already rejected, and read fixups use bpf_may_fault_on_deref() rather than this predicate. [ kkd: Rewrote commit log ]
Title bpf: Reject untrusted allocated-object pointers
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-25T10:23:51.126Z

Reserved: 2026-09-25T10:19:56.071Z

Link: CVE-2026-98037

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-25T11:17:32.443

Modified: 2026-09-25T11:17:32.443

Link: CVE-2026-98037

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T15:15:14Z

Weaknesses