diff options
| author | Jamal Hadi Salim <jhs@mojatatu.com> | 2026-10-12 14:09:25 -0400 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-19 19:39:45 -0700 |
| commit | f67b3ed1308d7a282e2d6202d61af052ab0da39e (patch) | |
| tree | 2ff4a63897f4c8d4e99270dace199b5ad5f1bc0e /include/linux | |
| parent | c0b628de2243f0d5d1c0e79e8acf9411f6b6f835 (diff) | |
net/sched: act_api: reject duplicate actions in a batch
tca_action_gd() builds actions[] with one tcf_action_get_1() per nested
TCA_ACT_TAB entry. Each successful lookup takes its own reference to the
resolved action, so repeated TCA_ACT_INDEX entries in one request yield
the same pointer in multiple slots.
For RTM_DELACTION, tcf_action_delete() then consumes two references per
slot: one in tcf_action_put() and one in tcf_idr_delete_index(). A
duplicate therefore drives the refcount to zero mid-walk -- the delete
frees the action and removes its IDR slot -- and the next slot calls
tcf_action_put() on the freed action:
refcount_t: underflow; use-after-free.
WARNING: lib/refcount.c:87 at refcount_dec_not_one
refcount_dec_and_mutex_lock
__tcf_action_put
tca_action_gd
Three duplicate entries are enough. Reject a repeated action while a
delete batch is built, dropping the reference the extra lookup took, and
return -EINVAL. RTM_GETACTION balances its own references and keeps
accepting duplicate entries.
Conditions to recreate the bug:
tc actions add action gact index 100
tc actions delete action gact index 100 action gact index 100 \
action gact index 100
Fixes: 16af6067392c ("net: sched: implement reference counted action release")
Reported-by: Sashiko (gemini) <sashiko-bot@kernel.org>
Link: https://sashiko.dev/#/patchset/20260824153903.4143642-1-victor@mojatatu.com
Signed-off-by: Jamal Hadi Salim <jhs@mojatatu.com>
Link: https://patch.msgid.link/QDISC-K1TH.v1.r3.20261012134653-1@mojatatu.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
