From: Ali Polatel via Bugspray Bot <bugbot@kernel.org>
To: bugs@lists.linux.dev, linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: MDWE does not prevent read-only, executable, shared memory regions to be updated by backing file writes
Date: Thu, 17 Jul 2025 13:15:08 +0000 [thread overview]
Message-ID: <20250717-b219227c5-426a315d1e51@bugzilla.kernel.org> (raw)
In-Reply-To: <20240912-b219227c0-78bee9e213fc@bugzilla.kernel.org>
Ali Polatel added an attachment on Kernel.org Bugzilla:
Created attachment 308384
Proof-of-Concept: MDWE bypass via file-backed RX mapping on Linux x86_64
Attached is a more complete POC which (ab)uses this bug to pop a shell. If I am correct, this means as an attacker I can use this to inject shellcode to most file-backed memory mappings and have it executed despite MDWE. Tested successfully on Linux-6.15.4 on x86_64.
File: mdwe-bypass-poc.c (text/x-csrc)
Size: 1.94 KiB
Link: https://bugzilla.kernel.org/attachment.cgi?id=308384
---
Proof-of-Concept: MDWE bypass via file-backed RX mapping on Linux x86_64
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-07-17 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 21:10 MDWE does not prevent read-only, executable, shared memory regions to be updated by backing file writes Bugspray Bot
2024-09-12 21:10 ` Bugspray Bot
2024-09-12 21:10 ` Bugspray Bot
2024-09-12 21:10 ` Bugspray Bot
2024-09-12 21:10 ` Bugspray Bot
2025-07-17 13:15 ` Ali Polatel via Bugspray Bot [this message]
2025-07-18 15:00 ` Ali Polatel via Bugspray Bot
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=20250717-b219227c5-426a315d1e51@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bugs@lists.linux.dev \
--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 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.