Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net: mvpp2: refill RX buffers before XDP or skb use

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: refill RX buffers before XDP or skb use The RX error path returns the current descriptor buffer to the hardware BM pool. That is only valid while the driver still owns the buffer. mvpp2_rx_refill() can fail after the current buffer has been handed to XDP or attached to an skb. In those cases mvpp2_run_xdp() may have recycled, redirected, or queued the page for XDP_TX, and an skb free also retires the data buffer. Returning such a buffer to BM lets hardware DMA into memory that is no longer owned by the RX ring. Refill the BM pool before handing the current buffer to XDP or to the skb. If the allocation fails there, drop the packet and return the still-owned current buffer to BM, preserving the pool depth. Once the refill succeeds, later local drops retire/free the current buffer instead of returning it to BM.

Affected products

Linux
  • =<6.6.*
  • <5e8e2a9624df72fca7c736b2966b2cbf6c9c3ff6
  • <5.8
  • =<6.18.*
  • ==5.9
  • <8a2126c5afe89f8ceeb60a3afb9f075b736194cd
  • =<*
  • =<6.1.*
  • <02e1b5c4d3b4c658b72c145427cded1bba613fc1
  • ==95a936364f2685e9e040c6b179b553604d96de22
  • <5.9
  • <580f92f27cb8724bcc4be98ee89890eab524a2ae
  • <d0c8c4fbd22d260fe28530260656c5fb3c20ce84
  • =<5.15.*
  • =<6.12.*
  • <a88b3293b556f4d8fba11db9a8061a6b0d3b69e6
  • <5.9
  • =<7.0.*
  • ==fba2cf348d9eb50b2049a73cc09313dab6d293f1
  • <a03cdcedb2cbcc42551dc3e4746929e93c5352d5