Skip to content
TrackCVE
  • 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-50206

arm64: fix oops in concurrently setting insn_emulation sysctls

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

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: fix oops in concurrently setting insn_emulation sysctls emulation_proc_handler() changes table->data for proc_dointvec_minmax and can generate the following Oops if called concurrently with itself: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010 | Internal error: Oops: 96000006 [#1] SMP | Call trace: | update_insn_emulation_mode+0xc0/0x148 | emulation_proc_handler+0x64/0xb8 | proc_sys_call_handler+0x9c/0xf8 | proc_sys_write+0x18/0x20 | __vfs_write+0x20/0x48 | vfs_write+0xe4/0x1d0 | ksys_write+0x70/0xf8 | __arm64_sys_write+0x20/0x28 | el0_svc_common.constprop.0+0x7c/0x1c0 | el0_svc_handler+0x2c/0xa0 | el0_svc+0x8/0x200 To fix this issue, keep the table->data as &insn->current_mode and use container_of() to retrieve the insn pointer. Another mutex is used to protect against the current_mode update but not for retrieving insn_emulation as table->data is no longer changing.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50206, 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.25% · top 84% of all CVEs (7 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.

Weakness

Affected products

  • Linux · Linux

    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < 9d5fec6ba2e4117d196a8259ab54615ffe562460
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < b51881b1da57fe9877125dfdd0aac5172958fcfd
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < 04549063d5701976034d8c2bfda3d3a8cbf0409f
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < 353b4673d01c512303c45cf2346f630cda73b5c9
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < cc69ef95988b9ef2fc730ec452a7441efb90ef5e
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < 6a2fd114678d7fc1b5a0f8865ae98f1c17787455
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < 07022e07017ee5540f5559b0aeb916e8383c1e1a
    • affected 587064b610c703f259317d00dc37bf6d40f4fc74 – < af483947d472eccb79e42059276c4deed76f99a6
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 4.14.291 – ≤ 4.14.*
    • unaffected 4.19.256 – ≤ 4.19.*
    • unaffected 5.4.211 – ≤ 5.4.*
    • unaffected 5.10.137 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (8)

Sources

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

Badge for a README or a ticket

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

Record last updated .