Re: [PATCH] net/llc: fix UBSAN array-index-out-of-bounds in llc_conn_state_process

From: Kartik Nair

Date: Sat May 16 2026 - 18:12:08 EST


Sure, by "direct path," I just meant the execution flow when
the socket isn't locked by the user (!sock_owned_by_user()).

In that case, llc_process_tmr_ev() immediately calls
llc_conn_state_process(). Right before making that call, it
checks if the state is LLC_CONN_OUT_OF_SVC and bails out if
it is. That's the path that is already safe.

The issue is with the backlog path. When the socket is busy,
the skb gets queued, but by the time the backlog drains and
finally calls llc_conn_state_process(), the state might have
changed to 0 via a teardown. Since there's no re-check there,
we end up hitting llc_offset_table[-1] and triggering UBSAN.

Putting the check right at the entry of llc_conn_state_process()
fixes it for both paths.

Kartik

On Sun, May 17, 2026 at 3:30 AM Kartik Nair <contact.kartikn@xxxxxxxxx> wrote:
>
> Sure, by "direct path," I just meant the execution flow when
> the socket isn't locked by the user (!sock_owned_by_user()).
>
> In that case, llc_process_tmr_ev() immediately calls
> llc_conn_state_process(). Right before making that call, it
> checks if the state is LLC_CONN_OUT_OF_SVC and bails out if
> it is. That's the path that is already safe.
>
> The issue is with the backlog path. When the socket is busy,
> the skb gets queued, but by the time the backlog drains and
> finally calls llc_conn_state_process(), the state might have
> changed to 0 via a teardown. Since there's no re-check there,
> we end up hitting llc_offset_table[-1] and triggering UBSAN.
>
> Putting the check right at the entry of llc_conn_state_process()
> fixes it for both paths.
>
> Kartik
>
> On Sun, May 17, 2026 at 3:00 AM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote:
>>
>> On 15/05/2026 19:49, Kartik Nair wrote:
>> > When a timer fires while the socket is owned by a user, the timer event
>> > is deferred to the backlog via __sk_add_backlog(). By the time the
>> > backlog drains, llc->state may have been set to LLC_CONN_OUT_OF_SVC (0)
>> > by socket teardown. llc_conn_state_process() then calls llc_conn_service()
>> > which computes llc_offset_table[state - 1] = llc_offset_table[-1],
>> > triggering UBSAN array-index-out-of-bounds.
>> >
>> > llc_process_tmr_ev() already guards against LLC_CONN_OUT_OF_SVC for the
>> > direct path, but this guard is bypassed when sock_owned_by_user() is true
>> > and the event is queued to the backlog. By the time the backlog drains,
>> > teardown may have set state to 0.
>> >
>> > The direct path already handles this case, so the same check belongs
>> > in the consumer too.
>>
>> Considering you sent similarly complex patches to MM, WiFi, accel and
>> now to NFC, I am sure you are using LLM without disclosing it.
>>
>> Please explain with your own words what is the "direct path"?
>>
>> Best regards,
>> Krzysztof