LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26900: md: fix kmemleak of rdev->serial

In the Linux kernel, the following vulnerability has been resolved: md: fix kmemleak of rdev->serial If kobject_add() is fail in bind_rdev_to_array(), 'rdev->serial' will be alloc not be freed, and kmemleak occurs. unreferenced object 0xffff88815a350000 (size 49152): comm "mdadm", pid 789, jiffies 4294716910 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc f773277a): [<0000000058b0a453>] kmemleak_alloc+0x61/0xe0 [<00000000366adf14>] __kmalloc_large_node+0x15e/0x270 [<000000002e82961b>] __kmalloc_node.cold+0x11/0x7f [<00000000f206d60a>] kvmalloc_node+0x74/0x150 [<0000000034bf3363>] rdev_init_serial+0x67/0x170 [<0000000010e08fe9>] mddev_create_serial_pool+0x62/0x220 [<00000000c3837bf0>] bind_rdev_to_array+0x2af/0x630 [<0000000073c28560>] md_add_new_disk+0x400/0x9f0 [<00000000770e30ff>] md_ioctl+0x15bf/0x1c10 [<000000006cfab718>] blkdev_ioctl+0x191/0x3f0 [<0000000085086a11>] vfs_ioctl+0x22/0x60 [<0000000018b656fe>] __x64_sys_ioctl+0xba/0xe0 [<00000000e54e675e>] do_syscall_64+0x71/0x150 [<000000008b0ad622>] entry_SYSCALL_64_after_hwframe+0x6c/0x74

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-26900 is a Linux kernel memory leak in the md RAID subsystem. If adding a device object fails, allocated serial memory may not be freed. Sources describe a resource leak, not code execution or data theft. There is no CISA KEV listing in the bundle.

Executive priority

Handle through normal kernel patch management unless the affected systems are critical storage hosts or exposed multi-tenant platforms. The known impact is memory leakage, but kernel resource exhaustion can still affect availability.

Technical view

The issue is in bind_rdev_to_array(): when kobject_add() fails, rdev->serial allocated through the md serial pool is not released, producing a kmemleak report on the mdadm to md_ioctl path. Fixed Linux stable commits are referenced across affected kernel branches.

Likely exposure

Exposure is most likely on systems running affected Linux kernels with md RAID functionality in use or available. The bundle lists affected Linux versions from 5.3 through fixed stable releases including 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.7.11, 6.8.2, and 6.9.

Exploitation context

The provided sources do not show active exploitation, public exploit activity, or remote attack paths. The observable path involves mdadm and kernel md ioctl handling. Treat exploitability details as incomplete unless vendor advisories provide more context.

Researcher notes

Evidence is limited to the upstream kernel fix description, stable commit links, and vendor advisories. No CVSS, CWE, exploit status, or detailed privilege requirement is provided in the bundle, so avoid overstating impact or reachability.

Mitigation direction

  • Update affected Linux kernels to vendor-supported fixed versions.
  • Prioritize systems using Linux md RAID or storage management workflows.
  • Review Debian, NetApp, and distribution advisories for packaged fixes.
  • Track kernel stable commits linked in the CVE record.
  • Use normal change controls for kernel rollout and reboot planning.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts using md RAID or mdadm-managed arrays.
  • Compare installed kernels against vendor fixed release guidance.
  • Confirm security updates from Debian or appliance vendors are applied.
  • Monitor for repeated md device add failures or kmemleak reports.
Prepared
Confidence
medium
Sources
11

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-26900 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

SSVC decision data

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

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
LinuxLinux963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5f, 963c555e75b033202dd76cf6325a7b7c83d08d5funaffected
LinuxLinux5.3, 0, 5.10.217, 5.15.159, 6.1.91, 6.6.31, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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