Linux KernelOperating system · Linux
CVE-2024-25740
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA memory leak flaw was found in the UBI driver in drivers/mtd/ubi/attach.c in the Linux kernel through 6.7.4 for UBI_IOCATT, because kobj->name is not released.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory leak exists in the Linux kernel's UBI (Unsorted Block Images) driver in drivers/mtd/ubi/attach.c. When the UBI_IOCATT ioctl is used to attach a UBI device, the kobj->name allocated during device attachment is not released, causing memory to accumulate with each attach operation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
<= 6.7.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the running kernel versionRun 'uname -r' or 'cat /proc/version' to obtain the kernel versionAffected if The kernel version is 6.7.4 or earlier (e.g., 6.7.4, 6.7.3, 6.6.x, etc.)
-
Verify if UBI (Unsorted Block Images) support is enabledCheck kernel config: 'grep -i ubi /boot/config-$(uname -r)' or look for 'ubi' in /proc/config.gz if availableAffected if CONFIG_MTD_UBI=y or CONFIG_MTD_UBI=m is set, meaning UBI support is compiled in
-
Check if UBI kernel module is loadedRun 'lsmod | grep ubi' or check /sys/module/ for ubi module presenceAffected if The ubi or ubi_msm module is loaded in memory
-
Identify if UBI devices exist or have been attachedCheck /sys/class/ubi/ or run 'ubiattach --help' to list UBI devices, or inspect dmesg for 'UBI' initialization messagesAffected if Any UBI devices (e.g., /dev/ubi0, /dev/ubi1) are present or were created via the UBI_IOCATT ioctl
You are affected if your kernel version is 6.7.4 or earlier, UBI support is enabled, and UBI devices have been attached using the UBI_IOCATT ioctl, causing unreleased kobj->name memory allocations to accumulate.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the upstream kernel patch that adds proper kfree() for kobj->name in the attach path, or update to a kernel version after 6.7.4 that includes the fix.
Kernel 6.7.5 or later (6.8.x stable recommended)
- Upgrade Linux kernel to version 6.7.5 or later, or to the latest stable kernel (6.8.x or later)
- After kernel upgrade, verify the UBI driver loads correctly and no memory leaks are observed
- If upgrading is not immediately possible, obtain the specific patch from lore.kernel.org for commit fixing kobj->name release in drivers/mtd/ubi/attach.c and apply it to the current kernel
- Reboot the system with the new kernel and monitor for memory stability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data