Answer in brief
CVE-2022-50206 records a Unknown severity vulnerability in arm64: fix oops in concurrently setting insn_emulation sysctls. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-50206 records a Unknown severity vulnerability in arm64: fix oops in concurrently setting insn_emulation sysctls. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=587064b610c703f259317d00dc37bf6d40f4fc74 <9d5fec6ba2e4117d196a8259ab54615ffe562460 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <b51881b1da57fe9877125dfdd0aac5172958fcfd || >=587064b610c703f259317d00dc37bf6d40f4fc74 <04549063d5701976034d8c2bfda3d3a8cbf0409f || >=587064b610c703f259317d00dc37bf6d40f4fc74 <353b4673d01c512303c45cf2346f630cda73b5c9 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <cc69ef95988b9ef2fc730ec452a7441efb90ef5e || >=587064b610c703f259317d00dc37bf6d40f4fc74 <6a2fd114678d7fc1b5a0f8865ae98f1c17787455 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <07022e07017ee5540f5559b0aeb916e8383c1e1a || >=587064b610c703f259317d00dc37bf6d40f4fc74 <af483947d472eccb79e42059276c4deed76f99a6 | 9d5fec6ba2e4117d196a8259ab54615ffe562460, b51881b1da57fe9877125dfdd0aac5172958fcfd, 04549063d5701976034d8c2bfda3d3a8cbf0409f, 353b4673d01c512303c45cf2346f630cda73b5c9, cc69ef95988b9ef2fc730ec452a7441efb90ef5e, 6a2fd114678d7fc1b5a0f8865ae98f1c17787455, 07022e07017ee5540f5559b0aeb916e8383c1e1a, af483947d472eccb79e42059276c4deed76f99a6 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=587064b610c703f259317d00dc37bf6d40f4fc74 <9d5fec6ba2e4117d196a8259ab54615ffe562460 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <b51881b1da57fe9877125dfdd0aac5172958fcfd || >=587064b610c703f259317d00dc37bf6d40f4fc74 <04549063d5701976034d8c2bfda3d3a8cbf0409f || >=587064b610c703f259317d00dc37bf6d40f4fc74 <353b4673d01c512303c45cf2346f630cda73b5c9 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <cc69ef95988b9ef2fc730ec452a7441efb90ef5e || >=587064b610c703f259317d00dc37bf6d40f4fc74 <6a2fd114678d7fc1b5a0f8865ae98f1c17787455 || >=587064b610c703f259317d00dc37bf6d40f4fc74 <07022e07017ee5540f5559b0aeb916e8383c1e1a || >=587064b610c703f259317d00dc37bf6d40f4fc74 <af483947d472eccb79e42059276c4deed76f99a6 | 9d5fec6ba2e4117d196a8259ab54615ffe562460, b51881b1da57fe9877125dfdd0aac5172958fcfd, 04549063d5701976034d8c2bfda3d3a8cbf0409f, 353b4673d01c512303c45cf2346f630cda73b5c9, cc69ef95988b9ef2fc730ec452a7441efb90ef5e, 6a2fd114678d7fc1b5a0f8865ae98f1c17787455, 07022e07017ee5540f5559b0aeb916e8383c1e1a, af483947d472eccb79e42059276c4deed76f99a6 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.