Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-23244— nvme: fix memory allocation in nvme_pr_read_keys()

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于nvme_pr_read_keys函数中未正确处理用户提供的num_keys值,可能导致内存分配过大。

AI Predicted 5.5 Difficulty: Moderate EPSS 0.13% · P2

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux 5fd96a4e15de8442915a912233d800c56f49001d< e42ff5abbd14927553b624c0e06d24df76156fe6 affected
5fd96a4e15de8442915a912233d800c56f49001d< 15fb6d627484ee39ed73e202ef4720e1fa5c898e affected
5fd96a4e15de8442915a912233d800c56f49001d< 5a501379a010690ae9ae88bef62a1bae1aca32e6 affected
5fd96a4e15de8442915a912233d800c56f49001d< baef52d80093bd686e70b3cb7e0512a40ae76705 affected
5fd96a4e15de8442915a912233d800c56f49001d< c3320153769f05fd7fe9d840cb555dd3080ae424 affected
6.5 affected
< 6.5 unaffected
6.6.130≤ 6.6.* unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-23244

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
nvme: fix memory allocation in nvme_pr_read_keys()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: nvme: fix memory allocation in nvme_pr_read_keys() nvme_pr_read_keys() takes num_keys from userspace and uses it to calculate the allocation size for rse via struct_size(). The upper limit is PR_KEYS_MAX (64K). A malicious or buggy userspace can pass a large num_keys value that results in a 4MB allocation attempt at most, causing a warning in the page allocator when the order exceeds MAX_PAGE_ORDER. To fix this, use kvzalloc() instead of kzalloc(). This bug has the same reasoning and fix with the patch below: https://lore.kernel.org/linux-block/20251212013510.3576091-1-kartikey406@gmail.com/ Warning log: WARNING: mm/page_alloc.c:5216 at __alloc_frozen_pages_noprof+0x5aa/0x2300 mm/page_alloc.c:5216, CPU#1: syz-executor117/272 Modules linked in: CPU: 1 UID: 0 PID: 272 Comm: syz-executor117 Not tainted 6.19.0 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:__alloc_frozen_pages_noprof+0x5aa/0x2300 mm/page_alloc.c:5216 Code: ff 83 bd a8 fe ff ff 0a 0f 86 69 fb ff ff 0f b6 1d f9 f9 c4 04 80 fb 01 0f 87 3b 76 30 ff 83 e3 01 75 09 c6 05 e4 f9 c4 04 01 <0f> 0b 48 c7 85 70 fe ff ff 00 00 00 00 e9 8f fd ff ff 31 c0 e9 0d RSP: 0018:ffffc90000fcf450 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffff920001f9ea0 RDX: 0000000000000000 RSI: 000000000000000b RDI: 0000000000040dc0 RBP: ffffc90000fcf648 R08: ffff88800b6c3380 R09: 0000000000000001 R10: ffffc90000fcf840 R11: ffff88807ffad280 R12: 0000000000000000 R13: 0000000000040dc0 R14: 0000000000000001 R15: ffffc90000fcf620 FS: 0000555565db33c0(0000) GS:ffff8880be26c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000002000000c CR3: 0000000003b72000 CR4: 00000000000006f0 Call Trace: <TASK> alloc_pages_mpol+0x236/0x4d0 mm/mempolicy.c:2486 alloc_frozen_pages_noprof+0x149/0x180 mm/mempolicy.c:2557 ___kmalloc_large_node+0x10c/0x140 mm/slub.c:5598 __kmalloc_large_node_noprof+0x25/0xc0 mm/slub.c:5629 __do_kmalloc_node mm/slub.c:5645 [inline] __kmalloc_noprof+0x483/0x6f0 mm/slub.c:5669 kmalloc_noprof include/linux/slab.h:961 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] nvme_pr_read_keys+0x8f/0x4c0 drivers/nvme/host/pr.c:245 blkdev_pr_read_keys block/ioctl.c:456 [inline] blkdev_common_ioctl+0x1b71/0x29b0 block/ioctl.c:730 blkdev_ioctl+0x299/0x700 block/ioctl.c:786 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+0x1bf/0x220 fs/ioctl.c:583 x64_sys_call+0x1280/0x21b0 mnt/fuzznvme_1/fuzznvme/linux-build/v6.19/./arch/x86/include/generated/asm/syscalls_64.h:17 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x71/0x330 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fb893d3108d Code: 28 c3 e8 46 1e 00 00 66 0f 1f 44 00 00 f3 0f 1e fa 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffff61f2f38 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffff61f3138 RCX: 00007fb893d3108d RDX: 0000000020000040 RSI: 00000000c01070ce RDI: 0000000000000003 RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ffff61f3138 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffff61f3128 R14: 00007fb893dae530 R15: 0000000000000001 </TASK>
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于nvme_pr_read_keys函数中未正确处理用户提供的num_keys值,可能导致内存分配过大。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 5fd96a4e15de8442915a912233d800c56f49001d ~ e42ff5abbd14927553b624c0e06d24df76156fe6 -
Linux Linux 6.5 -

II. Public POCs for CVE-2026-23244

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-23244

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-23244 (5)

Same Patch Batch · Linux · 2026-03-18 · 35 CVEs total

CVE-2026-23246 8.8 HIGH wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration
CVE-2026-23268 7.8 HIGH apparmor: fix unprivileged local user can do privileged policy management
CVE-2026-23270 7.8 HIGH net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks
CVE-2026-23253 7.8 HIGH media: dvb-core: fix wrong reinitialization of ringbuffer on reopen
CVE-2026-23248 7.8 HIGH perf/core: Fix refcount bug and potential UAF in perf_mmap
CVE-2026-23243 7.8 HIGH RDMA/umad: Reject negative data_len in ib_umad_write
CVE-2026-23245 7.8 HIGH net/sched: act_gate: snapshot parameters with RCU on replace
CVE-2025-71269 7.5 HIGH btrfs: do not free data reservation in fallback from inline due to -ENOSPC
CVE-2025-71268 7.5 HIGH btrfs: fix reservation leak in some error paths when inserting inline extent
CVE-2026-23242 7.5 HIGH RDMA/siw: Fix potential NULL pointer dereference in header processing
CVE-2026-23269 7.1 HIGH apparmor: validate DFA start states are in bounds in unpack_pdb
CVE-2026-23247 tcp: secure_seq: add back ports to TS offset
CVE-2025-71267 fs: ntfs3: fix infinite loop triggered by zero-sized ATTR_LIST
CVE-2026-23249 xfs: check for deleted cursors when revalidating two btrees
CVE-2026-23250 xfs: check return value of xchk_scrub_create_subord
CVE-2026-23251 xfs: only call xf{array,blob}_destroy if we have a valid pointer
CVE-2026-23252 xfs: get rid of the xchk_xfile_*_descr calls
CVE-2025-71266 fs: ntfs3: check return value of indx_find to avoid infinite loop
CVE-2025-71265 fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata
CVE-2025-71270 LoongArch: Enable exception fixup for specific ADE subcode

Showing top 20 of 35 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-23244

No comments yet


Leave a comment