SECUFOCUSNOW
Home›CVE index›CVE-2024-40901
Review reviewHigh

CVE-2024-40901

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory There is a potential out-of-bounds access when using test_bit() on a single word. The test_bit() and set_bit() functions operate on long values, and when testing or setting a single word, they can exceed the word boundary. KASAN detects this issue and produces a dump: 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...

CVSS
7.8
EPSS
0.31%
23.1% percentile
CISA KEV
Not listed
Published
2024.07.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.31%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory There is a potential out-of-bounds access when using test_bit() on a single word. The test_bit() and set_bit() functions operate on long values, and when testing or setting a single word, they can exceed the word boundary. KASAN detects this issue and produces a dump: 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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= c696f7b83edeac804e898952058089143f49ca0a < e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee, >= c696f7b83edeac804e898952058089143f49ca0a < 19649e49a6df07cd2e03e0a11396fd3a99485ec2, >= c696f7b83edeac804e898952058089143f49ca0a < 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16, >= c696f7b83edeac804e898952058089143f49ca0a < 521f333e644c4246ca04a4fc4772edc53dd2a801, >= c696f7b83edeac804e898952058089143f49ca0a < 46bab2bcd771e725ff5ca3a68ba68cfeac45676c, >= c696f7b83edeac804e898952058089143f49ca0a < 9079338c5a0d1f1fee34fb1c9e99b754efe414c5, >= c696f7b83edeac804e898952058089143f49ca0a < 18abb5db0aa9b2d48f7037a88b41af2eef821674, >= c696f7b83edeac804e898952058089143f49ca0a < 4254dfeda82f20844299dca6c38cbffcfd499f41, >= 4.10, >= 4.10 < 4.19.317, >= 4.20 < 5.4.279, >= 5.5 < 5.10.221, >= 5.11 < 5.15.162, >= 5.16 < 6.1.95, >= 6.2 < 6.6.35, >= 6.7 < 6.9.6, 6.10
Fixed versions
4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.9.6

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-787