watch_queue: Fix filter limit check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
watch_queue: Fix filter limit check
In watch_queue_set_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold. One place calculates the number of bits by:
if (tf[i].type >= sizeof(wfilter->type_filter) * 8)
which is fine, but the second does:
if (tf[i].type >= sizeof(wfilter->type_filter) * BITS_PER_LONG)
which is not. This can lead to a couple of out-of-bounds writes due to a too-large type:
(1) __set_bit() on wfilter->type_filter (2) Writing more elements in wfilter->filters[] than we allocated.
From the CVE record · Linux
The Linux kernel’s watch_queue_set_filter() uses an incorrect limit check for filter types. A local caller can supply an oversized type through an ioctl, causing out-of-bounds writes and potentially a kernel oops. The input does not specify authentication requirements or any user interaction.
Engineers running Linux kernels should check whether their kernel includes the watch_queue filter-limit fix; affected versions are not specified.