Skip to main content
VulnerabilityPublished Updated

CVE-2026-98044: Linux kernel · bpf: Reject legacy packet loads from callbacks

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e7d28823c662128caae63f14e16bd394916c139b, cebda2a2bb4183550eae9dcf888c16407b4fffda, bc489c0c9b8c86bd7fac42cfd1bb152f042fca56 +8

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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.12.101 <6.12.114
  • >=6.18.42 <6.18.53
  • >=5.10.265 <5.11
  • >=5.15.216 <5.16
  • >=6.1.183 <6.2
  • >=6.6.148 <6.7
  • >=7.0.10 <7.1
Fixed in
  • e7d28823c662128caae63f14e16bd394916c139b
  • cebda2a2bb4183550eae9dcf888c16407b4fffda
  • bc489c0c9b8c86bd7fac42cfd1bb152f042fca56
  • 3484a99303912db62428494a9061212049027e57
  • 7.1
  • 6.18.53
  • 6.12.114
  • 6.7
  • 6.2
  • 5.16
  • 5.11
LinuxLinuxAffected
  • =7.1
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject legacy packet loads from callbacks check_ld_abs() models a failed BPF_LD_ABS or BPF_LD_IND in a subprogram as an implicit return with R0 set to zero. It calls prepare_func_exit() to explore this synthesized path. When the load is reached directly from a synchronous callback, prepare_func_exit() enforces the callback return contract and marks R0 precise. R0 is not derived from a real instruction on this path, so precision backtracking reaches the callback call with R0 still requested and triggers the "callback unexpected regs" verifier bug. A privileged program loader can therefore cause a verifier warning and an -EFAULT BPF_PROG_LOAD. These legacy packet-load instructions are deprecated. Reject them from callbacks rather than complicating their implicit-return model. Check all active frames before constructing the implicit return so nested static subprograms cannot hide the callback context. Global functions are verified independently with a fresh frame zero, so an active-frame check cannot identify a global function called from a callback. Also check the complete subprogram call graph during stack-depth validation and reject a function containing a legacy load when any caller is a callback. This covers global and static descendants without making has_ld_abs transitive, preserving its per-function BTF return-type check. Ordinary uses outside callbacks remain supported.

References

Community reviews

Loading reviews…