All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudhir Dumbhare" <sudumbha@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap 03/21] nfs-utils: fix CVE-2025-12801
Date: Tue, 16 Jun 2026 00:43:33 -0700	[thread overview]
Message-ID: <82309.1781595813770605230@lists.openembedded.org> (raw)
In-Reply-To: <8dd3e431cafdd364285eeaa79bf89507a4f4c6a1.camel@pbarker.dev>

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

Hi Paul,
Thank you for pointing this out and for referencing both the original upstream commit and the RHEL backport.

When applying the upstream change, including prerequisites [1][2][3] and the fix [4], as noted in [6],
we observed the following compilation failure on scarthgap with nfs-utils v2.6.4:
nfsd_path.c:322:17: error: implicit declaration of function 'nfsd_run_task'

Because of this, we backported only the required changes from [5], specifically nfsd_run_task() and
struct nfsd_task_t, to support the fix. Non-essential parts were trimmed to keep the patch minimal
and build-safe for scarthgap.

Please let us know if you would prefer us to align with the full backport, similar to the RHEL approach.

References:
[1] https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=7e8b36522f58657359c6842119fc516c6dd1baa4
[2] https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=42f01e6a78fed98f12437ac8b28cfb12b6bad056
[3] https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=51738ae56d922d4961e60dad73ad1c2d97d8d99b
[4] Fixed by: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=f36bd900a899088ca1925de079bd58d6205a1f3c
[5] Dependent patch: https://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=cd90f29257904f36509ea5a04a86f42398fbe94a
[6] https://security-tracker.debian.org/tracker/CVE-2025-12801

Thanks and regards,
Sudhir

[-- Attachment #2: Type: text/html, Size: 1499 bytes --]

  reply	other threads:[~2026-06-16  7:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 14:25 [OE-core][scarthgap 00/21] Patch review Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 01/21] libpng: Fix CVE-2026-33416 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 02/21] busybox: Fix CVE-2026-29004 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 03/21] nfs-utils: fix CVE-2025-12801 Jeremy Rosen
2026-06-15  7:59   ` Paul Barker
2026-06-16  7:43     ` Sudhir Dumbhare [this message]
2026-06-12 14:25 ` [OE-core][scarthgap 04/21] xz: Fix CVE-2026-34743 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 05/21] util-linux: Fix CVE-2026-27456 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 06/21] devtool: prevent 'devtool modify -n' from corrupting kernel Git repos Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 07/21] go: patch CVE-2026-27142 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 08/21] go: patch CVE-2026-32280 Jeremy Rosen
2026-06-12 14:25 ` [OE-core][scarthgap 09/21] go: patch CVE-2026-32283 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 10/21] go: patch CVE-2026-32289 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 11/21] go: patch CVE-2026-33811 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 12/21] go: patch CVE-2026-39817 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 13/21] go: patch CVE-2026-39819 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 14/21] go: patch CVE-2026-39820 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 15/21] go: patch CVE-2026-39825 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 16/21] go: patch CVE-2026-39826 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 17/21] go: patch CVE-2026-42499 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 18/21] go: patch CVE-2026-42501 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 19/21] go: patch CVE-2026-42504 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 20/21] go: patch CVE-2026-42507 Jeremy Rosen
2026-06-12 14:26 ` [OE-core][scarthgap 21/21] meta/lib/oe/package.py: fix path to kernel sources in save_debugsources_info Jeremy Rosen

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=82309.1781595813770605230@lists.openembedded.org \
    --to=sudumbha@cisco.com \
    --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.