ring-buffer: Do not show buffer_meta for CPUs without a buffer
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3f23cae09a4677a3f7c163a68388512cb231ff22, Kernel 445bc0e0ed7b3f69b78a0fd8d3a8fdb4e20bc379, Kernel 8512d0312cc0ea83ca4511b164c29a138bbb0c21 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not show buffer_meta for CPUs without a buffer The per_cpu/cpuN/buffer_meta files are created for every possible CPU, but buffer->buffers[cpu] is only allocated once that CPU comes online. Reading the file of a CPU that never came online dereferences a NULL cpu_buffer in rbm_start(). Fail the open with -ENODEV when the CPU has no buffer, as the other per CPU ring buffer interfaces do.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.12, >=950032ffcee7a43c960951940059afc5a2bdbcbc <3f23cae09a4677a3f7c163a68388512cb231ff22, >=950032ffcee7a43c960951940059afc5a2bdbcbc <445bc0e0ed7b3f69b78a0fd8d3a8fdb4e20bc379, >=950032ffcee7a43c960951940059afc5a2bdbcbc <8512d0312cc0ea83ca4511b164c29a138bbb0c21, >=950032ffcee7a43c960951940059afc5a2bdbcbc <ae670c1a24fb5ffb167f26358cf47a5f0abbd670 | 3f23cae09a4677a3f7c163a68388512cb231ff22, 445bc0e0ed7b3f69b78a0fd8d3a8fdb4e20bc379, 8512d0312cc0ea83ca4511b164c29a138bbb0c21, ae670c1a24fb5ffb167f26358cf47a5f0abbd670 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket