Skip to content
Threat Brief

← All advisories

CVE-2026-98044

High 7.1No known exploitationFix available

bpf: Reject legacy packet loads from callbacks

Record last updated

CVSS score

7.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 5.10.265 before 5.115.11CVE Program
LinuxLinuxfrom 5.15.216 before 5.165.16CVE Program
LinuxLinuxfrom 6.1.183 before 6.26.2CVE Program
LinuxLinuxfrom 6.12.101 before 6.12.1146.12.114CVE Program
LinuxLinuxfrom 6.18.42 before 6.18.536.18.53CVE Program
LinuxLinuxfrom 6.6.148 before 6.76.7CVE Program
LinuxLinuxfrom 7.0.10 before 7.17.1CVE Program
LinuxLinuxfrom 8674e2db06cff6b50f2216eed9a761d15425bb34 before cebda2a2bb4183550eae9dcf888c16407b4fffdacebda2a2bb4183550eae9dcf888c16407b4fffdaCVE Program
LinuxLinuxfrom ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337 before 3484a99303912db62428494a9061212049027e573484a99303912db62428494a9061212049027e57CVE Program
LinuxLinuxfrom ee861486e377edc55361c08dcbceab3f6b6577bd before e7d28823c662128caae63f14e16bd394916c139be7d28823c662128caae63f14e16bd394916c139bCVE Program
LinuxLinuxfrom ee861486e377edc55361c08dcbceab3f6b6577bd before bc489c0c9b8c86bd7fac42cfd1bb152f042fca56bc489c0c9b8c86bd7fac42cfd1bb152f042fca56CVE Program
LinuxLinux37ad2bb11e9de92cb7b94548705eeedd87f7d392Not documentedCVE Program
LinuxLinux7.1Not documentedCVE Program
LinuxLinux8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbeNot documentedCVE Program
LinuxLinux928d354ae3557e8f755a227e67be88034eb3cd7fNot documentedCVE Program
LinuxLinuxd846d83bdacbd8f14fc45c63b8c1d22608452e1cNot documentedCVE Program
LinuxLinuxde1055e7f9e67af32b1f3376066272b04e5223c0Not documentedCVE Program
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documented6.6.159.1-1Microsoft MSRC
LinuxLinux (unaffected)from 6.12.114 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.7 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 7.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references