From: Juergen Gross <jgross@suse.com>
To: cve@kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: CVE-2022-49689: xen-blkfront: Handle NULL gendisk
Date: Wed, 26 Feb 2025 08:43:26 +0100 [thread overview]
Message-ID: <68bb3ad7-521d-4518-8b98-835b57f17455@suse.com> (raw)
In-Reply-To: <2025022627-CVE-2022-49689-06fb@gregkh>
[-- Attachment #1.1.1: Type: text/plain, Size: 1270 bytes --]
On 26.02.25 03:24, Greg Kroah-Hartman wrote:
> Description
> ===========
>
> In the Linux kernel, the following vulnerability has been resolved:
>
> xen-blkfront: Handle NULL gendisk
>
> When a VBD is not fully created and then closed, the kernel can have a
> NULL pointer dereference:
>
> The reproducer is trivial:
>
> [user@dom0 ~]$ sudo xl block-attach work backend=sys-usb vdev=xvdi target=/dev/sdz
> [user@dom0 ~]$ xl block-list work
> Vdev BE handle state evt-ch ring-ref BE-path
> 51712 0 241 4 -1 -1 /local/domain/0/backend/vbd/241/51712
> 51728 0 241 4 -1 -1 /local/domain/0/backend/vbd/241/51728
> 51744 0 241 4 -1 -1 /local/domain/0/backend/vbd/241/51744
> 51760 0 241 4 -1 -1 /local/domain/0/backend/vbd/241/51760
> 51840 3 241 3 -1 -1 /local/domain/3/backend/vbd/241/51840
> ^ note state, the /dev/sdz doesn't exist in the backend
>
> [user@dom0 ~]$ sudo xl block-detach work xvdi
Please revoke this CVE. As the reproducer recipe is clearly showing, the
bug can be triggered by host admin actions only. There is no way an unprivileged
user on the host or in the guest could trigger the issue.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
parent reply other threads:[~2025-02-26 7:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2025022627-CVE-2022-49689-06fb@gregkh>]
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=68bb3ad7-521d-4518-8b98-835b57f17455@suse.com \
--to=jgross@suse.com \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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®