{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2023-54223", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-12-30T12:06:44.501Z", "datePublished": "2025-12-30T12:11:17.389Z", "dateUpdated": "2026-08-05T09:18:11.613Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T09:18:11.613Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: xsk: Fix invalid buffer access for legacy rq\n\nThe below crash can be encountered when using xdpsock in rx mode for\nlegacy rq: the buffer gets released in the XDP_REDIRECT path, and then\nonce again in the driver. This fix sets the flag to avoid releasing on\nthe driver side.\n\nXSK handling of buffers for legacy rq was relying on the caller to set\nthe skip release flag. But the referenced fix started using fragment\ncounts for pages instead of the skip flag.\n\nCrash log:\n general protection fault, probably for non-canonical address 0xffff8881217e3a: 0000 [#1] SMP\n CPU: 0 PID: 14 Comm: ksoftirqd/0 Not tainted 6.5.0-rc1+ #31\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\n RIP: 0010:bpf_prog_03b13f331978c78c+0xf/0x28\n Code: ...\n RSP: 0018:ffff88810082fc98 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: ffff888138404901 RCX: c0ffffc900027cbc\n RDX: ffffffffa000b514 RSI: 00ffff8881217e32 RDI: ffff888138404901\n RBP: ffff88810082fc98 R08: 0000000000091100 R09: 0000000000000006\n R10: 0000000000000800 R11: 0000000000000800 R12: ffffc9000027a000\n R13: ffff8881217e2dc0 R14: ffff8881217e2910 R15: ffff8881217e2f00\n FS: 0000000000000000(0000) GS:ffff88852c800000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000564cb2e2cde0 CR3: 000000010e603004 CR4: 0000000000370eb0\n DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n Call Trace:\n \n ? die_addr+0x32/0x80\n ? exc_general_protection+0x192/0x390\n ? asm_exc_general_protection+0x22/0x30\n ? 0xffffffffa000b514\n ? bpf_prog_03b13f331978c78c+0xf/0x28\n mlx5e_xdp_handle+0x48/0x670 [mlx5_core]\n ? dev_gro_receive+0x3b5/0x6e0\n mlx5e_xsk_skb_from_cqe_linear+0x6e/0x90 [mlx5_core]\n mlx5e_handle_rx_cqe+0x55/0x100 [mlx5_core]\n mlx5e_poll_rx_cq+0x87/0x6e0 [mlx5_core]\n mlx5e_napi_poll+0x45e/0x6b0 [mlx5_core]\n __napi_poll+0x25/0x1a0\n net_rx_action+0x28a/0x300\n __do_softirq+0xcd/0x279\n ? sort_range+0x20/0x20\n run_ksoftirqd+0x1a/0x20\n smpboot_thread_fn+0xa2/0x130\n kthread+0xc9/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \n Modules linked in: mlx5_ib mlx5_core rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm ib_uverbs ib_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter overlay zram zsmalloc fuse [last unloaded: mlx5_core]\n ---[ end trace 0000000000000000 ]---" } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "baseScore": 9.8, "baseSeverity": "CRITICAL" }, "scenarios": [ { "lang": "en", "value": "AV:N - The corruption occurs in the mlx5e NAPI receive path while processing frames arriving from the wire — every packet the XDP program redirects into the AF_XDP socket performs the out-of-bounds increment and the premature buffer release. A remote host sending traffic to an mlx5 interface running AF_XDP zero-copy on legacy RQ (internet-facing L4 load balancers, 5G UPFs, DPDK AF_XDP PMD) drives the bug entirely over the network.\nAC:L - There is no race, no timing window and no dependence on memory layout the attacker cannot influence: each successfully redirected packet deterministically writes 2 bytes out of bounds and leaks a buffer release, and the attacker chooses the pointer displacement simply by choosing how many packets to send.\nPR:N - The XDP/AF_XDP zero-copy configuration is the operator's legitimate production setup, not an attacker action; the party that triggers the corruption only needs to send packets to the NIC and holds no credentials or account on the target.\nUI:N - The vulnerable code runs in softirq/NAPI context on packet reception with no involvement from any local user, so no victim interaction is required.\nS:U - The out-of-bounds write and the buffer-lifetime violation both corrupt kernel heap memory and the driver's own RX ring state, remaining within the kernel's security authority.\nC:H - The type-confused increment skews an in-use `struct xdp_buff *` by an attacker-chosen offset so kernel memory outside the buffer is read as packet metadata, and the prematurely released XSK chunk is re-handed to the NIC while userspace still owns the descriptor, exposing other packets' and kernel data to the application.\nI:H - The bug is an out-of-bounds heap write — a 2-byte increment past the end of the kvzalloc'ed `xsk_buffs[]` array and corruption of the adjacent buffer pointer — after which `xsk_buff_set_size()` writes through the skewed pointer and its DMA address is used as a device write target, yielding an attacker-influenced kernel write primitive.\nA:H - The upstream report documents a general protection fault on a non-canonical address in ksoftirqd, i.e. a kernel panic, and the aliased free-list entries additionally corrupt the XSK pool state." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/net/ethernet/mellanox/mlx5/core/en/xsk/rx.c" ], "versions": [ { "version": "cbb5379362513cbff450df0457dc370da7244bec", "lessThan": "58a113a35846d9a5bd759beb332e551e28451f09", "status": "affected", "versionType": "git" }, { "version": "7abd955a58fb0fcd4e756fa2065c03ae488fcfa7", "lessThan": "e0f52298fee449fec37e3e3c32df60008b509b16", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/net/ethernet/mellanox/mlx5/core/en/xsk/rx.c" ], "versions": [ { "version": "6.4.5", "lessThan": "6.4.10", "status": "affected", "versionType": "semver" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.4.5", "versionEndExcluding": "6.4.10" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/58a113a35846d9a5bd759beb332e551e28451f09" }, { "url": "https://git.kernel.org/stable/c/e0f52298fee449fec37e3e3c32df60008b509b16" } ], "title": "net/mlx5e: xsk: Fix invalid buffer access for legacy rq", "x_generator": { "engine": "bippy-1.2.0" } } } }