LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58001: ocfs2: handle a symlink read error correctly

In the Linux kernel, the following vulnerability has been resolved: ocfs2: handle a symlink read error correctly Patch series "Convert ocfs2 to use folios". Mark did a conversion of ocfs2 to use folios and sent it to me as a giant patch for review ;-) So I've redone it as individual patches, and credited Mark for the patches where his code is substantially the same. It's not a bad way to do it; his patch had some bugs and my patches had some bugs. Hopefully all our bugs were different from each other. And hopefully Mark likes all the changes I made to his code! This patch (of 23): If we can't read the buffer, be sure to unlock the page before returning.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-58001 is a Linux kernel OCFS2 filesystem bug in symlink error handling. If a symlink read fails, the kernel could return without unlocking the page. The public record does not provide CVSS, CWE, confirmed impact, or active exploitation evidence.

Executive priority

Treat this as a targeted kernel maintenance item rather than an emergency based on current evidence. Prioritize clustered storage systems using OCFS2 and fold remediation into the next approved kernel update cycle unless vendor guidance raises severity.

Technical view

The fix is in OCFS2 symlink handling: on buffer read failure, the page must be unlocked before returning. The affected component is the Linux kernel OCFS2 filesystem. Kernel stable commits and Debian LTS advisories are cited as remediation sources, but exploitability and security impact details are sparse.

Likely exposure

Exposure is most likely on Linux systems running affected kernels where OCFS2 is enabled or used, especially clustered storage environments. Systems not using OCFS2 are less likely exposed. Exact distribution-specific affected ranges require vendor advisory confirmation.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The public description suggests an error-path resource handling flaw, not a remotely reachable service issue. Practical impact is not fully established in the provided sources.

Researcher notes

Evidence is limited to the CVE record, kernel stable commits, and Debian LTS advisories. No CVSS, CWE, exploit narrative, or attacker prerequisites are provided. Analysis should avoid assuming privilege requirements, crash behavior, or weaponization without further vendor detail.

Mitigation direction

  • Update affected Linux kernels to vendor releases containing the OCFS2 fix.
  • Apply relevant Debian LTS kernel updates where Debian systems are in scope.
  • Check distribution advisories for backported fixes before relying on version numbers alone.
  • Prioritize systems that actively mount or depend on OCFS2 filesystems.
  • Monitor vendor guidance for any later severity or exploitability updates.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts with OCFS2 enabled, loaded, or mounted.
  • Confirm patched kernels include the referenced stable OCFS2 fix commits.
  • Review Debian LTS advisories if Debian is deployed.
  • Document systems where OCFS2 is unused to reduce remediation urgency.
Prepared
Confidence
medium
Sources
12

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-58001 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
1ADP providers
11Source links

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1, ea022dfb3c2a4680483b00eb2fecc9fc4f6091d1unaffected
LinuxLinux3.5, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

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