From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: CVE-2023-53212: xenbus: check xen_domain in xenbus_probe_initcall
Date: Mon, 15 Sep 2025 16:52:35 +0200 [thread overview]
Message-ID: <2025091522-banjo-waggle-ccfe@gregkh> (raw)
In-Reply-To: <33fb4d70-c3e7-4158-9727-3ad29f974246@suse.com>
On Mon, Sep 15, 2025 at 04:38:05PM +0200, Juergen Gross wrote:
> On 15.09.25 16:21, Greg Kroah-Hartman wrote:
> > From: Greg Kroah-Hartman <gregkh@kernel.org>
> >
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > xenbus: check xen_domain in xenbus_probe_initcall
> >
> > The same way we already do in xenbus_init.
> > Fixes the following warning:
> >
> > [ 352.175563] Trying to free already-free IRQ 0
> > [ 352.177355] WARNING: CPU: 1 PID: 88 at kernel/irq/manage.c:1893 free_irq+0xbf/0x350
> > [...]
> > [ 352.213951] Call Trace:
> > [ 352.214390] <TASK>
> > [ 352.214717] ? __warn+0x81/0x170
> > [ 352.215436] ? free_irq+0xbf/0x350
> > [ 352.215906] ? report_bug+0x10b/0x200
> > [ 352.216408] ? prb_read_valid+0x17/0x20
> > [ 352.216926] ? handle_bug+0x44/0x80
> > [ 352.217409] ? exc_invalid_op+0x13/0x60
> > [ 352.217932] ? asm_exc_invalid_op+0x16/0x20
> > [ 352.218497] ? free_irq+0xbf/0x350
> > [ 352.218979] ? __pfx_xenbus_probe_thread+0x10/0x10
> > [ 352.219600] xenbus_probe+0x7a/0x80
> > [ 352.221030] xenbus_probe_thread+0x76/0xc0
> >
> > The Linux kernel CVE team has assigned CVE-2023-53212 to this issue.
>
> I don't see how an unprivileged user could trigger this problem.
>
> Please revoke this CVE.
Now rejected, thanks for the review!
greg k-h
prev parent reply other threads:[~2025-09-15 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025091511-CVE-2023-53212-fdd4@gregkh>
2025-09-15 14:38 ` Juergen Gross
2025-09-15 14:52 ` Greg KH [this message]
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=2025091522-banjo-waggle-ccfe@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®