powerpc/papr_scm: Fix leaking nvdimm_events_map elements
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.18.3, Kernel 0e0946e22f3665d27325d389ff45ade6e93f3678 and Kernel b073096df4dec70d0436321b7093bad27ae91f9e.
In the Linux kernel, the following vulnerability has been resolved: powerpc/papr_scm: Fix leaking nvdimm_events_map elements Right now 'char *' elements allocated for individual 'stat_id' in 'papr_scm_priv.nvdimm_events_map[]' during papr_scm_pmu_check_events(), get leaked in papr_scm_remove() and papr_scm_pmu_register(), papr_scm_pmu_check_events() error paths. Also individual 'stat_id' arent NULL terminated 'char *' instead they are fixed 8-byte sized identifiers. However papr_scm_pmu_register() assumes it to be a NULL terminated 'char *' and at other places it assumes it to be a 'papr_scm_perf_stat.stat_id' sized string which is 8-byes in size. Fix this by allocating the memory for papr_scm_priv.nvdimm_events_map to also include space for 'stat_id' entries. This is possible since number of available events/stat_ids are known upfront. This saves some memory and one extra level of indirection from 'nvdimm_events_map' to 'stat_id'. Also rest of the code can continue to call 'kfree(papr_scm_priv.nvdimm_events_map)' without needing to iterate over the array and free up individual elements.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=5.18 <5.18.3, =5.18, >=4c08d4bbc089a95f3f38389c2b79dbc6ab24f10b <0e0946e22f3665d27325d389ff45ade6e93f3678, >=4c08d4bbc089a95f3f38389c2b79dbc6ab24f10b <b073096df4dec70d0436321b7093bad27ae91f9e | 5.18.3, 0e0946e22f3665d27325d389ff45ade6e93f3678, b073096df4dec70d0436321b7093bad27ae91f9e |
| linux-kernel: Kernel | >=5.18.0 <5.18.3 | 5.18.3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket