{ "schema_version": "1.6.1", "id": "RPI-CVE-2024-40901", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2024-40901" ], "published": "2024-07-12T12:21:19Z", "summary": "scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory\n\nThere is a potential out-of-bounds access when using test_bit() on a single\nword. The test_bit() and set_bit() functions operate on long values, and\nwhen testing or setting a single word, they can exceed the word\nboundary. KASAN detects this issue and produces a dump:\n\n\t BUG: KASAN: slab-out-of-bounds in _scsih_add_device.constprop.0 (./arch/x86/include/asm/bitops.h:60 ./include/asm-generic/bitops/instrumented-atomic.h:29 drivers/scsi/mpt3sas/mpt3sas_scsih.c:7331) mpt3sas\n\n\t Write of size 8 at addr ffff8881d26e3c60 by task kworker/u1536:2/2965\n\nFor full log, please look at [1].\n\nMake the allocation at least the size of sizeof(unsigned long) so that\nset_bit() and test_bit() have sufficient room for read/write operations\nwithout overwriting unallocated memory.\n\n[1] Link: https://lore.kernel.org/all/ZkNcALr3W3KGYYJG@gmail.com/", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.47-1+rpt4" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" } ] }, "database_specific": { "per_version": { "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.95", "compiled_filter": false } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2024-40901" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/19649e49a6df07cd2e03e0a11396fd3a99485ec2" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/521f333e644c4246ca04a4fc4772edc53dd2a801" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/46bab2bcd771e725ff5ca3a68ba68cfeac45676c" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/9079338c5a0d1f1fee34fb1c9e99b754efe414c5" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/18abb5db0aa9b2d48f7037a88b41af2eef821674" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/4254dfeda82f20844299dca6c38cbffcfd499f41" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:52:36Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.3, "cvss_v3_severity": "High", "scenario": "AV:L - The undersized bitmaps are per-HBA kernel objects touched by local device-discovery/reset work and by the `MPT3COMMAND` ioctl on `/dev/mpt3ctl`, which passes a user-supplied `device_handle` to `test_bit()`. Nothing here processes remote network data, so local access is required.\nAC:L - On any controller whose firmware reports a `MaxDevHandle` that is not a multiple of 64, the allocation is deterministically short and every device add/remove or handle-referencing ioctl performs the 8-byte read-modify-write past the requested allocation. No race, no memory-layout grooming, and no unpredictable system state is involved.\nPR:L - The driver performs no `capable()`/`CAP_SYS_RAWIO` check on any of these paths \u2014 reachability is governed solely by device-node policy, and appliance, storage-management and container deployments routinely hand `/dev/mpt3ctl` or HBA-attached block devices to a non-root storage group. The OOB write side itself occurs in automatic discovery work that needs no privilege at all, so low privileges are the ceiling of what an attacker needs.\nUI:N - Device discovery, hotplug handling and controller reset run autonomously in the driver's firmware-event workqueue, and the ioctl path is a plain syscall. No victim action of any kind is required.\nS:U - The out-of-bounds access corrupts kernel slab memory from within kernel context; there is no crossing of a VM, IOMMU, or sandbox boundary.\nC:L - `test_bit()` reads an 8-byte word that extends past the allocation, but the overread is strictly bounded to at most 7 adjacent bytes and only the in-bounds bit is consumed, so no meaningful memory contents are returned to the attacker.\nI:H - This is an out-of-bounds write \u2014 KASAN reports `Write of size 8` past the slab allocation from `_scsih_add_device` \u2014 and the atomic RMW spans neighbouring heap bytes, which can clobber a concurrent non-atomic update to adjacent slab memory. Per the out-of-bounds-write classification this is scored High.\nA:H - The trailing word access crosses the object boundary, which faults into the guard page under KFENCE (enabled by default in mainstream distro and Android kernels) and raises a slab-out-of-bounds BUG under KASAN or SLUB redzoning, producing an oops or, with `panic_on_warn`, a full kernel panic." } } }