Skip to main content
VulnerabilityPublished Updated

CVE-2026-98038: Linux kernel · bpf: Keep refcount_acquire nullable for borrowed RCU kptrs

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in dc36739e5cc9f60485418a910b42bc95339218d2 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in dc36739e5cc9f60485418a910b42bc95339218d2, 85074498228a2500ea8b8039c49cc1ab8ad5328f, 85bfc8b6db43502444c428eaa2de20bdd2fb9064 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to dc36739e5cc9f60485418a910b42bc95339218d2, 85074498228a2500ea8b8039c49cc1ab8ad5328f, 85bfc8b6db43502444c428eaa2de20bdd2fb9064 or 8d19e2cdfba9ba8c8eb6a459cd666bec00a1d2c6.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1b12171533a9bb23cf6fba7262b479028b65e1e8, < dc36739e5cc9f60485418a910b42bc95339218d2
Fixed in
  • dc36739e5cc9f60485418a910b42bc95339218d2
LinuxLinuxAffected
  • ≥ 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 85074498228a2500ea8b8039c49cc1ab8ad5328f
Fixed in
  • 85074498228a2500ea8b8039c49cc1ab8ad5328f
LinuxLinuxAffected
  • ≥ 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 85bfc8b6db43502444c428eaa2de20bdd2fb9064
Fixed in
  • 85bfc8b6db43502444c428eaa2de20bdd2fb9064
LinuxLinuxAffected
  • ≥ 1b12171533a9bb23cf6fba7262b479028b65e1e8, < 8d19e2cdfba9ba8c8eb6a459cd666bec00a1d2c6
Fixed in
  • 8d19e2cdfba9ba8c8eb6a459cd666bec00a1d2c6
LinuxLinuxAffected
  • =6.8
Fixed in–

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 ]

References

Community reviews

Loading reviews…