Linux kernel
cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*, +4 more
A vulnerability in the Linux kernel's ring buffer handling has been addressed. The issue arose in the function 'ring_buffer_map_get_reader()', which was overly strict compared to similar functions. Under normal circumstances, 'rb_get_reader_page()' should not return NULL, as this would trigger a warning. However, the warning was incorrectly activated when the reader caught up to the writer, leaving data still available on the reader page. In such cases, 'rb_get_reader_page()' returns NULL because there are no new pages to retrieve. The reader page should remain unchanged, and no warning should be issued.
This vulnerability could lead to unnecessary warning messages being generated, which could obscure other important log information.
The vulnerability can be reproduced by using the ring buffer mapping functions in a scenario where the reader catches up to the writer, but there is still data to be read on the reader page. This will cause 'rb_get_reader_page()' to return NULL, triggering a warning that should not occur in this situation.
Users can update to the latest version of the Linux kernel where this vulnerability has been fixed.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.