From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 68421@debbugs.gnu.org
Subject: bug#68421: Possible use after free in w32notify.c
Date: Sat, 13 Jan 2024 11:12:31 +0200 [thread overview]
Message-ID: <83jzodha0w.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk+yj2=W2y6irp56N7jKGs7kWFNqnBwZt8SuYAne_wkCw@mail.gmail.com> (message from Stefan Kangas on Sat, 13 Jan 2024 01:49:36 -0600)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 13 Jan 2024 01:49:36 -0600
>
> Could someone familiar with w32notify.c look over the attached patch?
>
> It looks like we are trying to dereference NULL in add_watch, and
> returning an already freed value from start_watching.
Feel free to install on master, and thanks.
next prev parent reply other threads:[~2024-01-13 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 7:49 bug#68421: Possible use after free in w32notify.c Stefan Kangas
2024-01-13 9:12 ` Eli Zaretskii [this message]
2024-01-13 9:25 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83jzodha0w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68421@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).