Skip to content
Threat Brief

← All advisories

CVE-2026-92486

Severity unknownNo known exploitationFix available

bpf: Fix CFI mismatch in task work callback

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 11% 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: Fix CFI mismatch in task work callback BPF subprograms use the bpf_callback_t ABI, but task work invokes the callback through a three-argument function pointer. This trips kCFI. Store and invoke the callback as bpf_callback_t.

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 38aa7003e369802f81a078f6673d10d97013f04f before 85a33c910edc3651f68b17ae3c597c012545958f85a33c910edc3651f68b17ae3c597c012545958fCVE Program
LinuxLinuxfrom 38aa7003e369802f81a078f6673d10d97013f04f before a2cbab47f44e9ea8c5a161ecba1b6bb8535771eba2cbab47f44e9ea8c5a161ecba1b6bb8535771ebCVE Program
LinuxLinuxfrom 38aa7003e369802f81a078f6673d10d97013f04f before 2805abd089576799b15092949420e3f8ba97fabd2805abd089576799b15092949420e3f8ba97fabdCVE Program
LinuxLinux6.18Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.18.52 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.6 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.18Not 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. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references