Emacs arbitrary code execution flaw (lwn.net)
<p>Sean Whitton has <a
href="https://lwn.net/ml/all/87tsnskt3e.fsf%40athena.silentflame.com/">announced</a>
that the original fix for an arbitrary code execution flaw in Emacs (<a
href="https://nvd.nist.gov/vuln/detail/cve-2024-53920">CVE-2024-53920</a>) was
incomplete. Bas Alberts discovered that viewing or editing untrusted files in
modes other than Emacs's Lisp mode can also result in arbitrary code
execution.</p>
<blockquote class="bq">
<p>This problem affects all Emacs versions affected by CVE-2024-53920.
This means Emacs 24 and newer, and possibly also older versions.</p>
<p>A minimal fix, attached, is queued up for release with Emacs 31.2.
We (the Emacs upstream maintainers) don't expect to backport the fix to
older Emacs releases ourselves.</p>
</blockquote>
<p>LWN <a href="https://lwn.net/Articles/1002046/">covered</a> the original
vulnerability in December 2024.</p>
href="https://lwn.net/ml/all/87tsnskt3e.fsf%40athena.silentflame.com/">announced</a>
that the original fix for an arbitrary code execution flaw in Emacs (<a
href="https://nvd.nist.gov/vuln/detail/cve-2024-53920">CVE-2024-53920</a>) was
incomplete. Bas Alberts discovered that viewing or editing untrusted files in
modes other than Emacs's Lisp mode can also result in arbitrary code
execution.</p>
<blockquote class="bq">
<p>This problem affects all Emacs versions affected by CVE-2024-53920.
This means Emacs 24 and newer, and possibly also older versions.</p>
<p>A minimal fix, attached, is queued up for release with Emacs 31.2.
We (the Emacs upstream maintainers) don't expect to backport the fix to
older Emacs releases ourselves.</p>
</blockquote>
<p>LWN <a href="https://lwn.net/Articles/1002046/">covered</a> the original
vulnerability in December 2024.</p>
Comments