LiveActive security incident?Get immediate response
CVE Record

CVE-2024-49965: ocfs2: remove unreasonable unlock in ocfs2_read_blocks

In the Linux kernel, the following vulnerability has been resolved: ocfs2: remove unreasonable unlock in ocfs2_read_blocks Patch series "Misc fixes for ocfs2_read_blocks", v5. This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix. This patch (of 2): There was a lock release before exiting, so remove the unreasonable unlock.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-49965 is a Linux kernel locking error in the OCFS2 filesystem’s block-reading path. The supplied CVSS assessment indicates that a local, low-privileged attacker could potentially affect confidentiality, integrity, and availability. Systems not using affected kernels or OCFS2 are less likely to be exposed.

Executive priority

Treat this as a high-priority kernel maintenance issue on systems using OCFS2, especially sensitive or shared-storage hosts. It is not supported as an emergency internet-wide threat because access is local and active exploitation is not reported. Establish exposure promptly, then apply supported kernel updates through normal expedited change control.

Technical view

The flaw is an incorrect lock release in ocfs2_read_blocks(). A lock had already been released before the function exited, creating an unlock imbalance. The kernel fix removes the extra unlock. The sources do not establish the precise crash, corruption, or privilege-escalation mechanism, so those outcomes should not be asserted individually.

Likely exposure

Exposure is most likely on systems running a listed affected Linux kernel where OCFS2 is present and its block-reading path is reachable. The bundle lists affected releases from 4.20 through several maintained branches and 6.12, but vendor backports may alter status. Confirm exact packaged kernels with the distributor.

Exploitation context

The CVSS vector describes local access, low complexity, low privileges, and no user interaction. The supplied KEV status is false, and no cited source reports active exploitation. The issue was found through syzbot lock-balance detection and subsequent review, indicating evidence of a defect but not confirmed malicious use.

Researcher notes

The record identifies an extra unlock in ocfs2_read_blocks() and supplies fixes across stable branches. Its affected-version data mixes release numbers and commit identifiers, limiting reliable range interpretation without vendor packaging context. No CWE is assigned. Researchers should distinguish the demonstrated lock imbalance from unproven outcomes such as privilege escalation or data corruption.

Mitigation direction

  • Install the distributor-supported kernel update containing the applicable stable fix.
  • Check vendor advisories for backported fixes before judging exposure by version number alone.
  • Prioritize shared-storage or sensitive systems that actively use OCFS2.
  • If immediate updating is impossible, consult vendor guidance for supported temporary risk reduction.

Validation and detection

  • Inventory kernel versions and identify systems configured to use OCFS2.
  • Compare each packaged kernel against its distributor’s CVE or security advisory.
  • Verify the installed kernel contains the applicable stable fix or documented backport.
  • After updating, confirm systems booted into the remediated kernel.
  • Review kernel logs for OCFS2 locking warnings or related instability.
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-49965 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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
12Source 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.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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

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

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6c150df9c2e80b5cf86f5a0d98beb7390ad63bfc, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, cf76c78595ca87548ca5e45c862ac9e0949c4687, 01f93d5e36753fc4d06ec67f05ce78c9c6f2dd56, 65cbd1279f4b999d56a838344a30642db24cd215, 97e1db17bc1ef4c2e1789bc9323c7be44fba53f8, 4.19.87, 4.4.204, 4.9.204, 4.14.157unaffected
LinuxLinux4.20, 0, 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, 6.11.3, 6.12affected
Weakness

CWE details

No CWE listed

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