From this webpage screenshot, we can extract the following key information about the vulnerability: 1. **Vulnerability Description**: - The vulnerability describes a scenario during kernel build where, if `CONFIG_FORCE_NR_CPUS` is set to `y`, `nr_cpu_ids` is defined as `NR_CPUS` instead of the actual possible number of CPUs, leading to system crashes. - Specifically, this manifests as accessing a non-existent `percpu rtpcp` variable in the `rcu_tasks_need_gpcb()` function. 2. **Error Messages**: - The system crash generates the following error messages: - `BUG: unable to handle page fault for address: ffffffff9911c8c8` - `CPU: 0 PID: 15 Comm: rcu_tasks_trace Tainted: G W` - `RIP: 0010:rcu_tasks_need_gpcb+0x25d/0x2c0` - `RSP: 0018:ffffa371c00a3e60 EFLAGS: 00010082` - `CR2: ffffffff9911c8c8 CR3: 00000000000001706f0` 3. **Fixes**: - Fixed the issue in the `rcu_tasks_need_gpcb()` function where it accesses a non-existent `percpu rtpcp` variable. - Modified the definition of the `rcu_tasks_percpu` structure to ensure that, in cases where CPU numbering may have gaps, the maximum possible CPU count is used instead of `nr_cpu_ids`. 4. **Patch Content**: - Modifications were made to the `rcu_tasks.h` file, including the definition of the `rcu_tasks_percpu` structure and initialization of the `rcu_task_cpu_ids` variable. 5. **Patch Application**: - The patch was applied to the `rcu_tasks.h` file, resolving the bug that could cause system crashes under specific conditions. This information indicates that the vulnerability is related to the kernel's RCU (Read-Copy Update) mechanism, and the fix addresses a crash condition that could occur under specific configurations.