LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27389: pstore: inode: Only d_invalidate() is needed

In the Linux kernel, the following vulnerability has been resolved: pstore: inode: Only d_invalidate() is needed Unloading a modular pstore backend with records in pstorefs would trigger the dput() double-drop warning: WARNING: CPU: 0 PID: 2569 at fs/dcache.c:762 dput.part.0+0x3f3/0x410 Using the combo of d_drop()/dput() (as mentioned in Documentation/filesystems/vfs.rst) isn't the right approach here, and leads to the reference counting problem seen above. Use d_invalidate() and update the code to not bother checking for error codes that can never happen. ---

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel pstorefs bug. Under specific conditions, unloading a modular pstore backend while pstore records exist can mishandle internal file references and trigger a kernel warning. The source bundle does not provide CVSS, CWE, impact severity, or exploitation evidence, so urgency should be based on affected-kernel presence and vendor guidance.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not an emergency based on current evidence. Prioritize patching systems with custom kernels, modular pstore backends, or operational workflows that unload pstore backends.

Technical view

The issue is in Linux kernel pstore inode handling. The vulnerable path used d_drop()/dput(), causing a reference-count double-drop warning during modular pstore backend unload with records in pstorefs. Stable fixes replace that handling with d_invalidate() and remove unreachable error checking.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds where pstore is enabled, pstorefs contains records, and the pstore backend is modular. The bundle lists affected Linux kernel versions and multiple stable commit references, but does not name distributions, appliances, or cloud images.

Exploitation context

The provided data says this CVE is not in KEV and gives no public exploitation reports. The described trigger is operational and local to kernel/pstore backend behavior. No evidence supports internet-facing exploitation or remote attack assumptions.

Researcher notes

Evidence is limited to the CVE description and Linux stable commits. The sources describe a reference-counting warning path, not a demonstrated privilege escalation, denial of service, or data exposure. Distribution-specific impact and fixed package versions require vendor advisories.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable pstore fixes.
  • Confirm Linux distribution advisories for backported fixes before relying on version numbers alone.
  • Avoid unloading modular pstore backends on affected production systems until patched.
  • Review vendor guidance if custom kernels or appliance kernels are used.

Validation and detection

  • Inventory systems running Linux kernels in the affected version ranges from the CVE record.
  • Check whether pstore and pstorefs are enabled or used on those systems.
  • Verify whether the running kernel includes one of the referenced stable fixes or a vendor backport.
  • Review kernel logs for related pstorefs or dput double-drop warnings.
Prepared
Confidence
medium
Sources
8

Public sources used

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-27389 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
7Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux609e28bb139e53621521130f0d4aea27a725d465, 609e28bb139e53621521130f0d4aea27a725d465, 609e28bb139e53621521130f0d4aea27a725d465, 609e28bb139e53621521130f0d4aea27a725d465, 609e28bb139e53621521130f0d4aea27a725d465, 609e28bb139e53621521130f0d4aea27a725d465unaffected
LinuxLinux5.8, 0, 5.15.209, 6.1.83, 6.6.23, 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.