From: Paul Barker <paul@pbarker.dev>
To: Junjie Cao <junjie.cao@linux.dev>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] cve-exclusions: set status for CVE-2022-0400
Date: Mon, 24 Aug 2026 09:31:08 +0100 [thread overview]
Message-ID: <f94020c9d3d9a7a9a49c1ddfaa56b2af3d7cfe2c.camel@pbarker.dev> (raw)
In-Reply-To: <20260824043034.1457687-1-junjie.cao@linux.dev>
On Sun, 2026-08-23 at 23:30 -0500, Junjie Cao wrote:
> The CVE describes an out-of-bounds read in the SMC protocol stack, but
> the originating report, Red Hat bug 2040604, was never made public and
> no tracker records affected code or a fix.
>
> On request, Red Hat PSIRT identified the affected code (ticket
> PSIRTSUPT-22046, summarized in the public bug [1]): the v2_ext_offset
> field of an incoming CLC proposal message is used to compute a memory
> offset without validation, in the chain smc_clc_msg_hdr_valid() ->
> smc_clc_msg_prop_valid() -> smc_get_clc_v2_ext() (net/smc/smc_clc.h).
>
> The unchecked read dates from the introduction of V2 CLC proposal
> parsing in v5.10 (8c3dca341aea); at the time of the report,
> smc_get_clc_v2_ext() checked the offset only for zero and
> smc_clc_msg_prop_valid() dereferenced the resulting pointer. It is
> closed by the v6.13 validation of exactly these fields:
>
> https://git.kernel.org/linus/7863c9f3d24ba49dbead7e03dfbe40deb5888fdf
> ("net/smc: check v2_ext_offset/eid_cnt/ism_gid_cnt when receiving
> proposal msg", v6.13)
>
> The kernel CVE team assigned that commit CVE-2024-49568, recording the
> issue introduced in 5.10 and fixed in 6.6.68, 6.12.7 and 6.13:
>
> https://lore.kernel.org/linux-cve-announce/2025011142-CVE-2024-49568-e5f6@gregkh/
>
> CVE-2022-0400 predates the kernel CNA and no tracker has connected it
> to this fix.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2044575#c23
>
> CC: Paul Barker <paul@pbarker.dev>
> AI-Generated: Uses Claude (claude-opus-5)
> Signed-off-by: Junjie Cao <junjie.cao@linux.dev>
Thanks for following this up!
One nitpick...
> +# The originating report (Red Hat bug 2040604) is not public. On request,
> +# Red Hat PSIRT identified the affected code: the v2_ext_offset of an
> +# incoming SMC CLC proposal message was used without validation in
> +# net/smc/smc_clc.h. Introduced in v5.10, fixed by the v6.13 proposal
> +# message validation, which upstream tracks as CVE-2024-49568.
> +# https://bugzilla.redhat.com/show_bug.cgi?id=2044575#c23
> +# Fix https://git.kernel.org/linus/7863c9f3d24ba49dbead7e03dfbe40deb5888fdf
> +CVE_STATUS[CVE-2022-0400] = "fixed-version: Fixed from version 6.13"
We can say 6.13rc4 here.
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-08-24 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 4:30 [OE-core][PATCH] cve-exclusions: set status for CVE-2022-0400 Junjie Cao
2026-08-24 8:31 ` Paul Barker [this message]
2026-08-24 16:25 ` Junjie Cao
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=f94020c9d3d9a7a9a49c1ddfaa56b2af3d7cfe2c.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=junjie.cao@linux.dev \
--cc=openembedded-core@lists.openembedded.org \
/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.