CVE-2026-98038

bpf: Keep refcount_acquire nullable for borrowed RCU kptrs

State
Published
Severity
Not scored
Published
Sep 25, 2026
Updated
Oct 21, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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

bpf: Keep refcount_acquire nullable for borrowed RCU kptrs

bpf_refcount_acquire() is fallible for a borrowed reference because the object may have reached a zero refcount. The verifier therefore keeps KF_RET_NULL on the return value unless the argument is an owning reference.

An RCU-protected load of a local kptr is marked MEM_ALLOC, but it only receives NON_OWN_REF when the pointee contains a graph node. A refcounted object without a graph node consequently looks like an owning reference even though the loaded register has no acquired reference state. If the program drops the last real reference while remaining in the RCU critical section, refcount_inc_not_zero() returns NULL while the verifier treats the result as non-NULL.

Only classify the argument as owning when it is backed by a verifier-tracked reference. This retains the non-NULL return for pointers from bpf_obj_new(), bpf_kptr_xchg(), or an earlier successful acquisition, while requiring a NULL check for borrowed RCU kptrs.

[ kkd: Rewrote commit log ]

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 1b12171533a9bb23cf6fba7262b479028b65e1e8 to before 85bfc8b6db43502444c428eaa2de20bdd2fb9064Affected
  • 1b12171533a9bb23cf6fba7262b479028b65e1e8 to before 8d19e2cdfba9ba8c8eb6a459cd666bec00a1d2c6Affected
  • 1b12171533a9bb23cf6fba7262b479028b65e1e8 to before 85074498228a2500ea8b8039c49cc1ab8ad5328fAffected
  • 1b12171533a9bb23cf6fba7262b479028b65e1e8 to before dc36739e5cc9f60485418a910b42bc95339218d2Affected
LinuxLinux
  • 6.8Affected
  • before 6.8Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.57 through 6.18.*Not affected
  • 7.2.7 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.