All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junjie Cao <junjie.cao@linux.dev>
To: openembedded-core@lists.openembedded.org
Cc: paul@pbarker.dev
Subject: [OE-core][PATCH v4 3/8] cve-exclusions: set status for CVE-2021-3864
Date: Sun, 23 Aug 2026 23:21:18 -0500	[thread overview]
Message-ID: <20260824042123.1456876-4-junjie.cao@linux.dev> (raw)
In-Reply-To: <20260824042123.1456876-1-junjie.cao@linux.dev>

begin_new_exec() resets dumpability to owner-dumpable whenever the real
and effective ids match at exec time. A binary exec'd by a setuid
program that has already called setuid(0) therefore becomes dumpable as
root, and with a relative core_pattern plus an attacker-controlled
working directory the resulting core file can be dropped into a
privileged directory such as /etc/logrotate.d.

Full report with proof of concept:

  https://www.openwall.com/lists/oss-security/2021/10/20/2

Two fixes were proposed and neither was merged. Waiman Long's patch
was judged "not a particularly effective mitigation" by Eric W.
Biederman and the discussion went quiet by early 2022; Wander Lairson
Costa's RFC v2 received design feedback and no v3 followed:

  https://lore.kernel.org/all/20211221021744.864115-1-longman@redhat.com/
  https://lore.kernel.org/all/20211228170910.623156-1-wander@redhat.com/

CC: Paul Barker <paul@pbarker.dev>
AI-Generated: Uses Claude (claude-opus-5)
Signed-off-by: Junjie Cao <junjie.cao@linux.dev>
---
v4:
- use the review's comment and status wording; drop the coredump path
  analysis paragraph
- quote Biederman's assessment verbatim

v3: https://lore.kernel.org/openembedded-core/20260812072842.1176341-1-junjie.cao@linux.dev/

 meta/recipes-kernel/linux/cve-exclusion.inc | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/meta/recipes-kernel/linux/cve-exclusion.inc b/meta/recipes-kernel/linux/cve-exclusion.inc
index 36643ccc..36920e2c 100644
--- a/meta/recipes-kernel/linux/cve-exclusion.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion.inc
@@ -206,3 +206,11 @@ model, no upstream fix"
 # https://ubuntu.com/security/CVE-2021-3714
 CVE_STATUS[CVE-2021-3714] = "unpatched: Timing side channel inherent to Kernel \
 Same-page Merging (KSM) page deduplication"
+
+# Triaged August 2026 - Two fixes proposed upstream but neither was merged,
+# attempts to fix seem to have petered out. Unfixed in Debian/Ubuntu.
+# https://lore.kernel.org/all/20211221021744.864115-1-longman@redhat.com/
+# https://lore.kernel.org/all/20211228170910.623156-1-wander@redhat.com/
+# https://security-tracker.debian.org/tracker/CVE-2021-3864
+# https://ubuntu.com/security/CVE-2021-3864
+CVE_STATUS[CVE-2021-3864] = "unpatched: Proposed fixes were not merged upstream"
-- 
2.43.0



  parent reply	other threads:[~2026-08-24  2:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  4:21 [OE-core][PATCH v4 0/8] cve-exclusions: triage eight kernel CVEs lacking upstream fix data Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 1/8] cve-exclusions: set status for CVE-2019-14899 Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 2/8] cve-exclusions: set status for CVE-2021-3714 Junjie Cao
2026-08-24  4:21 ` Junjie Cao [this message]
2026-08-24  4:21 ` [OE-core][PATCH v4 4/8] cve-exclusions: set status for CVE-2022-1247 Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 5/8] cve-exclusions: set status for CVE-2022-4543 Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 6/8] cve-exclusions: set status for CVE-2023-3397 Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 7/8] cve-exclusions: set status for CVE-2023-6238 Junjie Cao
2026-08-24  4:21 ` [OE-core][PATCH v4 8/8] cve-exclusions: set status for CVE-2023-6240 Junjie Cao
2026-08-24  7:57 ` [OE-core][PATCH v4 0/8] cve-exclusions: triage eight kernel CVEs lacking upstream fix data Paul Barker

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=20260824042123.1456876-4-junjie.cao@linux.dev \
    --to=junjie.cao@linux.dev \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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.