arm64: fix oops in concurrently setting insn_emulation sysctls
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.291, 4.19.256, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 5.4.211
- CVEs
- CVE-2022-50206
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:29 UTC · Revision 1
Source evidence
arm64: fix oops in concurrently setting insn_emulation sysctls
core-osv · Original sourcePublished 18 Jun 2025, 11:03 UTC
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.
osv:CVE-2022-50206
Kernel
Fixed versions: 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2
Complete source record
{
"id": "a6490ba1df761b243a6c0b7bc9d36d8890343cb294e0a58e82147d3c2c68f0e1",
"url": "https://osv.dev/vulnerability/CVE-2022-50206",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "arm64: fix oops in concurrently setting insn_emulation sysctls",
"summary": "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.",
"evidence": "osv:CVE-2022-50206",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.291",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.256",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.211",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.137",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.61",
"evidence": "/affected/1/ranges"
},
{
"value": "5.18.18",
"evidence": "/affected/1/ranges"
},
{
"value": "5.19.2",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-50206",
"aliases": [
"CVE-2022-50206"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "587064b610c703f259317d00dc37bf6d40f4fc74"
},
{
"fixed": "9d5fec6ba2e4117d196a8259ab54615ffe562460"
},
{
"fixed": "b51881b1da57fe9877125dfdd0aac5172958fcfd"
},
{
"fixed": "04549063d5701976034d8c2bfda3d3a8cbf0409f"
},
{
"fixed": "353b4673d01c512303c45cf2346f630cda73b5c9"
},
{
"fixed": "cc69ef95988b9ef2fc730ec452a7441efb90ef5e"
},
{
"fixed": "6a2fd114678d7fc1b5a0f8865ae98f1c17787455"
},
{
"fixed": "07022e07017ee5540f5559b0aeb916e8383c1e1a"
},
{
"fixed": "af483947d472eccb79e42059276c4deed76f99a6"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50206.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.19.0"
},
{
"fixed": "4.14.291"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.256"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.211"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.137"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.61"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.18.18"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.19.0"
},
{
"fixed": "5.19.2"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50206.json"
}
}
],
"modified": "2026-10-28T02:30:49.731274265Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/04549063d5701976034d8c2bfda3d3a8cbf0409f",
"https://git.kernel.org/stable/c/07022e07017ee5540f5559b0aeb916e8383c1e1a",
"https://git.kernel.org/stable/c/353b4673d01c512303c45cf2346f630cda73b5c9",
"https://git.kernel.org/stable/c/6a2fd114678d7fc1b5a0f8865ae98f1c17787455",
"https://git.kernel.org/stable/c/9d5fec6ba2e4117d196a8259ab54615ffe562460",
"https://git.kernel.org/stable/c/af483947d472eccb79e42059276c4deed76f99a6",
"https://git.kernel.org/stable/c/b51881b1da57fe9877125dfdd0aac5172958fcfd",
"https://git.kernel.org/stable/c/cc69ef95988b9ef2fc730ec452a7441efb90ef5e",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50206.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-50206",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50206.json"
}
},
"related_cves": [
{
"value": "CVE-2022-50206",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 517763,
"published_at": "2025-06-18T11:03:46.505+00:00"
}