linux-cve-announce - CVE-2023-53212: xenbus: check xen_domain in xenbus_probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091511-CVE-2023-53212-fdd4@gregkh>
Date: Mon, 15 Sep 2025 16:21:46 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53212: xenbus: check xen_domain in xenbus_probe_initcall

From: Greg Kroah-Hartman <gregkh@...nel.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.


Affected and fixed versions
===========================

	Issue introduced in 5.19 with commit 5b3353949e89d48b4faf54a9cc241ee5d70df615 and fixed in 6.1.43 with commit 37b5a0bdb896bfe646649ff15bb55b7032b512dc
	Issue introduced in 5.19 with commit 5b3353949e89d48b4faf54a9cc241ee5d70df615 and fixed in 6.4.8 with commit 7a72e63d926b728d24f73d2d6052f5e14be0c502
	Issue introduced in 5.19 with commit 5b3353949e89d48b4faf54a9cc241ee5d70df615 and fixed in 6.5 with commit 0d8f7cc8057890db08c54fe610d8a94af59da082

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2023-53212
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/xen/xenbus/xenbus_probe.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/37b5a0bdb896bfe646649ff15bb55b7032b512dc
	https://git.kernel.org/stable/c/7a72e63d926b728d24f73d2d6052f5e14be0c502
	https://git.kernel.org/stable/c/0d8f7cc8057890db08c54fe610d8a94af59da082