From: Greg KH <gregkh@linuxfoundation.org>
To: Xingyu Li <xli399@ucr.edu>
Cc: stable@vger.kernel.org, tung.q.nguyen@dektech.com.au,
Jakub Kicinski <kuba@kernel.org>, Zheng Zhang <zzhan173@ucr.edu>
Subject: Re: Patch "tipc: fix kernel warning when sending SYN message" should be probably ported to 5.10 and 5.15 LTS
Date: Wed, 22 Jan 2025 08:45:06 +0100 [thread overview]
Message-ID: <2025012231-tiger-litigate-a372@gregkh> (raw)
In-Reply-To: <CALAgD-4Wd2M01V2P8DRCMU0Lg+zJzGYSNgGQCdEpRWxrrkjHvA@mail.gmail.com>
On Tue, Jan 21, 2025 at 11:13:38PM -0800, Xingyu Li wrote:
> Hi,
>
> We noticed that the patch 11a4d6f67cf5 should be ported to 5.10 and
> 5.15 LTS according to the bug introducing commit. Also, it can be
> applied
> to the latest version of these two LTS branches without conflicts. Its
> bug introducing commit is f25dcc7687d4. The kernel warning and stack
> trace indicate a problem when sending a SYN message in TIPC
> (Transparent Inter-Process Communication). The issue arises because
> `copy_from_iter()` is being called with an uninitialized `iov_iter`
> structure, leading to invalid memory operations. The commit
> (`f25dcc7687d4`) introduces the vulnerability by replacing the old
> data copying mechanisms with the new `copy_from_iter()` function
> without ensuring that the `iov_iter` structure is properly initialized
> in all code paths. The patch adds initialization of `iov_iter` with
> "iov_iter_kvec(&m.msg_iter, ITER_SOURCE, NULL, 0, 0);", which ensures
> that even when there's no data to send, the `iov_iter` is correctly
> set up, preventing the kernel warning/crash when `copy_from_iter()` is
> called.
This change fails to build on those older kernels, which is perhaps why
it was not backported there. If you wish to see it there, please
provide a working backport.
thanks,
greg k-h
prev parent reply other threads:[~2025-01-22 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 7:13 Patch "tipc: fix kernel warning when sending SYN message" should be probably ported to 5.10 and 5.15 LTS Xingyu Li
2025-01-22 7:45 ` Greg KH [this message]
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=2025012231-tiger-litigate-a372@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tung.q.nguyen@dektech.com.au \
--cc=xli399@ucr.edu \
--cc=zzhan173@ucr.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.