LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40901: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory

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:7331) mpt3sas Write of size 8 at addr ffff8881d26e3c60 by task kworker/u1536:2/2965 For full log, please look at [1]. Make the allocation at least the size of sizeof(unsigned long) so that set_bit() and test_bit() have sufficient room for read/write operations without overwriting unallocated memory. [1] Link: https://lore.kernel.org/all/ZkNcALr3W3KGYYJG@gmail.com/

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux SCSI driver can access memory beyond a small allocation while adding a device. This may corrupt kernel memory, potentially causing crashes or unauthorized changes. The supplied CVSS score is 7.3, but the issue requires local, low-privileged access and relevant mpt3sas usage.

Executive priority

Treat this as a high-priority kernel maintenance issue on storage systems using mpt3sas, especially where untrusted users have local access. It is less urgent for systems without that driver or hardware path. Expedite vendor-supported updates, but do not characterize it as an actively exploited emergency.

Technical view

In mpt3sas _scsih_add_device, test_bit() and set_bit() operate on unsigned-long-sized values while the target allocation may hold only one smaller word. This can produce an eight-byte slab out-of-bounds access. The kernel fix allocates at least sizeof(unsigned long). KASAN detected the defect in a kernel worker.

Likely exposure

Exposure is most likely on systems running an affected Linux kernel with the mpt3sas SCSI driver and its device-add path in use. The bundle lists affected releases from 4.10 through several stable lines ending at 6.10, but administrators should verify downstream backports rather than rely solely on version numbers.

Exploitation context

The supplied vector describes a local, low-complexity attack requiring low privileges and no user interaction. Potential impacts are low confidentiality loss and high integrity and availability loss. The bundle marks KEV false and provides no evidence of active exploitation or a public working exploit.

Researcher notes

The evidence demonstrates an out-of-bounds kernel memory access and supplies fixes across stable branches. It does not establish a reliable exploitation primitive, exact attacker-controlled inputs, or exploitation in the wild. The affected-version data is unusually presented, so branch ancestry and distribution backports require direct verification.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Check distribution advisories because fixed code may be backported without changing the upstream version pattern.
  • Prioritize systems actively using mpt3sas for attached storage.
  • If patching is delayed, follow vendor guidance for safe interim risk reduction.

Validation and detection

  • Inventory running kernel versions across Linux systems.
  • Determine whether mpt3sas is present and used for active storage controllers.
  • Compare vendor changelogs against the referenced stable kernel fixes.
  • Confirm the corrected kernel is running after maintenance.
  • Review kernel logs for matching KASAN or slab-out-of-bounds reports.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-40901 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H1.85.5Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2024-40901Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0a, c696f7b83edeac804e898952058089143f49ca0aunaffected
LinuxLinux4.10, 0, 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35, 6.9.6, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.