Vulnerability · Published Mar 25, 2026 · Assigned by Linux

CVE-2026-23327cxl/mbox: validate payload size before accessing contents in cxl_payload_from_user_allowed()

High 7.1

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.1High
Exploit odds (30 days)0.2%top 94.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: cxl/mbox: validate payload size before accessing contents in cxl_payload_from_user_allowed() cxl_payload_from_user_allowed() casts and dereferences the input payload without first verifying its size. When a raw mailbox command is sent with an undersized payload (ie: 1 byte for CXL_MBOX_OP_CLEAR_LOG, which expects a 16-byte UUID), uuid_equal() reads past the allocated buffer, triggering a KASAN splat: BUG: KASAN: slab-out-of-bounds in memcmp+0x176/0x1d0 lib/string.c:683 Read of size 8 at addr ffff88810130f5c0 by task syz.1.62/2258 CPU: 2 UID: 0 PID: 2258 Comm: syz.1.62 Not tainted 6.19.0-dirty #3 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xab/0xe0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xce/0x650 mm/kasan/report.c:482 kasan_report+0xce/0x100 mm/kasan/report.c:595 memcmp+0x176/0x1d0 lib/string.c:683 uuid_equal include/linux/uuid.h:73 [inline] cxl_payload_from_user_allowed drivers/cxl/core/mbox.c:345 [inline] cxl_mbox_cmd_ctor drivers/cxl/core/mbox.c:368 [inline] cxl_validate_cmd_from_user drivers/cxl/core/mbox.c:522 [inline] cxl_send_cmd+0x9c0/0xb50 drivers/cxl/core/mbox.c:643 __cxl_memdev_ioctl drivers/cxl/core/memdev.c:698 [inline] cxl_memdev_ioctl+0x14f/0x190 drivers/cxl/core/memdev.c:713 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa8/0x330 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fdaf331ba79 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fdaf1d77038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fdaf3585fa0 RCX: 00007fdaf331ba79 RDX: 00002000000001c0 RSI: 00000000c030ce02 RDI: 0000000000000003 RBP: 00007fdaf33749df R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fdaf3586038 R14: 00007fdaf3585fa0 R15: 00007ffced2af768 </TASK> Add 'in_size' parameter to cxl_payload_from_user_allowed() and validate the payload is large enough.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-23327
Debian:13linux6.12.115-2DEBIAN-CVE-2026-23327
Debian:14linux6.19.8-1DEBIAN-CVE-2026-23327
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-23327
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-23327
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-23327
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-23327

Affected products (as reported)

VendorProductVersions
Linux Linux 6179045ccc0c6229dc449afc1701dc7fbd40571f – before c0874ca9282ccf5aeae559c697dd1feb577aad0e6179045ccc0c6229dc449afc1701dc7fbd40571f – before 3555e41737c0f8b5b53a511573661477e3942dee6179045ccc0c6229dc449afc1701dc7fbd40571f – before 483b7eb4b1b2a03235afe1b274732dcf8231d4ec6179045ccc0c6229dc449afc1701dc7fbd40571f – before dc184ac2f0ba77ae19725ee06ad3ab36bb9d1f616179045ccc0c6229dc449afc1701dc7fbd40571f – before 7c8a7b7f063b7e7ae9bba4cbaa14a5d2fe3a55e16179045ccc0c6229dc449afc1701dc7fbd40571f – before 60b5d1f68338aff2c5af0113f04aefa7169c50c2
Linux Linux 5.19

References