From: Ye Weihua <yeweihua4@huawei.com>
To: <gregkh@linuxfoundation.org>, <brauner@kernel.org>, <kees@kernel.org>
Cc: <cve@kernel.org>, <linux-mm@kvack.org>, <yeweihua4@huawei.com>
Subject: [PATCH] CVE-2026-74484: Fix introducing commit via .vulnerable
Date: Wed, 19 Aug 2026 03:01:03 +0000 [thread overview]
Message-ID: <20260819030103.422702-1-yeweihua4@huawei.com> (raw)
The introduced tag of CVE-2026-74484 is 21ca59b365c0
("binfmt_misc: enable sandboxed mounts", v6.7), not 948b701a607f,
because before sandboxed mounts an unprivileged user or container cannot
trigger the self-referential DoS in a restricted namespace.
Signed-off-by: Ye Weihua <yeweihua4@huawei.com>
---
cve/published/2026/CVE-2026-74484.vulnerable | 1 +
1 file changed, 1 insertion(+)
create mode 100644 cve/published/2026/CVE-2026-74484.vulnerable
diff --git a/cve/published/2026/CVE-2026-74484.vulnerable b/cve/published/2026/CVE-2026-74484.vulnerable
new file mode 100644
index 000000000..39fb39f38
--- /dev/null
+++ b/cve/published/2026/CVE-2026-74484.vulnerable
@@ -0,0 +1 @@
+21ca59b365c091d583f36ac753eaa8baf947be6f
--
2.34.1
next reply other threads:[~2026-08-19 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 3:01 Ye Weihua [this message]
2026-08-19 6:51 ` [PATCH] CVE-2026-74484: Fix introducing commit via .vulnerable Greg KH
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=20260819030103.422702-1-yeweihua4@huawei.com \
--to=yeweihua4@huawei.com \
--cc=brauner@kernel.org \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox