On Tue, Sep 19, 2023 at 12:23:18PM +0300, Igor Artemiev wrote: > The value of pxmitframe->attrib.priority in r8712_issue_addbareq_cmd(), > which dump_xframe() calls, is used to calculate the index for accessing > an array of size 16. The value of pxmitframe->attrib.priority can be > greater than 15, because the r8712_update_attrib() function can write > a value up to 31 to attrib.priority, and r8712_xmitframe_complete() > checks that pxmitframe->attrib.priority is less than 16 before > calling r8712_xmitframe_coalesce(). But that number comes from the hardware, so how can it ever be larger than 15? > Found by Linux Verification Center (linuxtesting.org) with SVACE. How was this tested to verify that it can be triggered and that this change solves anything? You have read the kernel documentation for what is required when using "research tools" like this, right? thanks, greg k-h
