Netdev List
 help / color / mirror / Atom feed
From: Victor Nogueira <victor@mojatatu.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>
Cc: Mingi Cho <mgcho.minic@gmail.com>,
	security@kernel.org, Jiri Pirko <jiri@resnulli.us>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: Use-after-free in Linux tc subsystem (v6.15)
Date: Mon, 30 Jun 2025 08:52:22 -0300	[thread overview]
Message-ID: <1a169adc-fe99-4058-a6a7-e32bb694e997@mojatatu.com> (raw)
In-Reply-To: <CAM0EoM=jc7=JdHMdXM9hmcP2ZGF0BnByXWbMZUN44LvaGHe-DQ@mail.gmail.com>

On 6/30/25 08:06, Jamal Hadi Salim wrote:
> On Sun, Jun 29, 2025 at 5:08 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>>
>> On Sat, Jun 28, 2025 at 05:26:59PM -0400, Jamal Hadi Salim wrote:
>>> On Thu, Jun 26, 2025 at 1:11 AM Mingi Cho <mgcho.minic@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> I think the testcase I reported earlier actually contains two
>>>> different bugs. The first is returning SUCCESS with an empty TBF qdisc
>>>> in tbf_segment, and the second is returning SUCCESS with an empty QFQ
>>>> qdisc in qfq_enqueue.
>>>>
>>>
>>> Please join the list where a more general solution is being discussed here:
>>> https://lore.kernel.org/netdev/aF847kk6H+kr5kIV@pop-os.localdomain/
>>
>> I think that one is different, the one here is related to GSO, the above
>> linked one is not. Let me think about the GSO issue, since I already
>> looked into it before.
> 
> TBH, they all look the same to me - at minimal, they should be tested
> against Lion's patch first. Maybe there's a GSO corner case but wasnt
> clear to me.

I did a quick test of Lion's patch using Mingi's C reproducer.
The patch seems to fix the UAF.

cheers,
Victor

  reply	other threads:[~2025-06-30 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE1YQVoTz5REkvZWzq_X5f31Sr6NzutVCxxmLfWtmVZkjiingA@mail.gmail.com>
     [not found] ` <CAM_iQpV8NpK_L2_697NccDPfb9SPYhQ7BT1Ssueh7nT-rRKJRA@mail.gmail.com>
     [not found]   ` <CAM_iQpXVaxTVALH9_Lki+O=1cMaVx4uQhcRvi4VcS2rEdYkj5Q@mail.gmail.com>
     [not found]     ` <CAM_iQpVi0V7DNQFiNWWMr+crM-1EFbnvWV5_L-aOkFsKaA3JBQ@mail.gmail.com>
     [not found]       ` <CAM0EoMm4D+q1eLzfKw3gKbQF43GzpBcDFY3w2k2OmtohJn=aJw@mail.gmail.com>
     [not found]         ` <CAM0EoMkFzD0gKfJM2-Dtgv6qQ8mjGRFmWF7+oe=qGgBEkVSimg@mail.gmail.com>
     [not found]           ` <CAE1YQVq=FmrGw56keHQ2gEGtrdg3H5Nf_OcPb8_Rn5NVQ4AoHg@mail.gmail.com>
2025-06-28 21:26             ` Use-after-free in Linux tc subsystem (v6.15) Jamal Hadi Salim
2025-06-29 21:08               ` Cong Wang
2025-06-30 11:06                 ` Jamal Hadi Salim
2025-06-30 11:52                   ` Victor Nogueira [this message]
2025-06-30 22:10                     ` Cong Wang
2025-06-30 18:50               ` Victor Nogueira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1a169adc-fe99-4058-a6a7-e32bb694e997@mojatatu.com \
    --to=victor@mojatatu.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=mgcho.minic@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox