Ben Greear writes:
> On 08/02/2018 01:20 PM, Toke Høiland-Jørgensen wrote:
>> Ben Greear writes:
>>
>>> On 08/02/2018 12:45 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
> This is from my hacked kernel, could be my fault. I thought the fq
> guys might want to know
On 08/02/2018 01:20 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
On 08/02/2018 12:45 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
This is from my hacked kernel, could be my fault. I thought the fq
guys might want to know however...
Hmm, nothing obvious comes to mind;
Ben Greear writes:
> On 08/02/2018 12:45 PM, Toke Høiland-Jørgensen wrote:
>> Ben Greear writes:
>>
>>> This is from my hacked kernel, could be my fault. I thought the fq
>>> guys might want to know however...
>>
>> Hmm, nothing obvious comes to mind; fq_flow_dequeue() just dequeues a
>> packet
On 08/02/2018 12:45 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
This is from my hacked kernel, could be my fault. I thought the fq
guys might want to know however...
Hmm, nothing obvious comes to mind; fq_flow_dequeue() just dequeues a
packet from the queue; it only has two memory
Ben Greear writes:
> This is from my hacked kernel, could be my fault. I thought the fq
> guys might want to know however...
Hmm, nothing obvious comes to mind; fq_flow_dequeue() just dequeues a
packet from the queue; it only has two memory derefs, to fq->lock and
flow->queue. Don't see why
This is from my hacked kernel, could be my fault. I thought the fq guys might
want to know however...
==
BUG: KASAN: use-after-free in fq_flow_dequeue+0x353/0x3c0 [mac80211]
Read of size 4 at addr 88013d92a700 by task rmmod/813
