ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()
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:
ptr_ring: do not block hard interrupts in ptr_ring_resize_multiple()
Jakub added a lockdep_assert_no_hardirq() check in __page_pool_put_page() to increase test coverage.
syzbot found a splat caused by hard irq blocking in ptr_ring_resize_multiple() [1]
As current users of ptr_ring_resize_multiple() do not require hard irqs being masked, replace it to only block BH.
Rename helpers to better reflect they are safe against BH only.
- ptr_ring_resize_multiple() to ptr_ring_resize_multiple_bh() - skb_array_resize_multiple() to skb_array_resize_multiple_bh()
[1]
From the CVE record · Linux
The Linux kernel’s ptr_ring resize function can block hard interrupts when its current users do not require that. A syzbot test triggered a kernel warning while resizing a TUN device queue. The input does not establish whether an attacker can trigger this, what access would be needed, or whether user interaction is required.
Engineers running Linux kernels with the affected ptr_ring resize code should check their kernel vendor’s advisory for affected versions.