Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49552

bpf: Fix combination of jit blinding and pointers to bpf subprogs.

Medium5.5EPSS 0.26%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix combination of jit blinding and pointers to bpf subprogs. The combination of jit blinding and pointers to bpf subprogs causes: [ 36.989548] BUG: unable to handle page fault for address: 0000000100000001 [ 36.990342] #PF: supervisor instruction fetch in kernel mode [ 36.990968] #PF: error_code(0x0010) - not-present page [ 36.994859] RIP: 0010:0x100000001 [ 36.995209] Code: Unable to access opcode bytes at RIP 0xffffffd7. [ 37.004091] Call Trace: [ 37.004351] <TASK> [ 37.004576] ? bpf_loop+0x4d/0x70 [ 37.004932] ? bpf_prog_3899083f75e4c5de_F+0xe3/0x13b The jit blinding logic didn't recognize that ld_imm64 with an address of bpf subprogram is a special instruction and proceeded to randomize it. By itself it wouldn't have been an issue, but jit_subprogs() logic relies on two step process to JIT all subprogs and then JIT them again when addresses of all subprogs are known. Blinding process in the first JIT phase caused second JIT to miss adjustment of special ld_imm64. Fix this issue by ignoring special ld_imm64 instructions that don't have user controlled constants and shouldn't be blinded.

Scores

CVSS scores of CVE-2022-49552, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.26% · top 82% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 69c087ba6225b574afb6e505b72cb75242a3d844 – < a029b02b47dd5bb87a21550d9d9a80cb4dd3f714
    • affected 69c087ba6225b574afb6e505b72cb75242a3d844 – < d106a3e96fca30e44081eae9c27aab28fc132a46
    • affected 69c087ba6225b574afb6e505b72cb75242a3d844 – < 4b6313cf99b0d51b49aeaea98ec76ca8161ecb80
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.17.13 – ≤ 5.17.*
    • unaffected 5.18.2 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References (3)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49552 badge
[![CVE-2022-49552](https://trackcve.app/badge/CVE-2022-49552.svg)](https://trackcve.app/cve/CVE-2022-49552)

Record last updated .