LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58094: jfs: add check read-only before truncation in jfs_truncate_nolock()

In the Linux kernel, the following vulnerability has been resolved: jfs: add check read-only before truncation in jfs_truncate_nolock() Added a check for "read-only" mode in the `jfs_truncate_nolock` function to avoid errors related to writing to a read-only filesystem. Call stack: block_write_begin() { jfs_write_failed() { jfs_truncate() { jfs_truncate_nolock() { txEnd() { ... log = JFS_SBI(tblk->sb)->log; // (log == NULL) If the `isReadOnly(ip)` condition is triggered in `jfs_truncate_nolock`, the function execution will stop, and no further data modification will occur. Instead, the `xtTruncate` function will be called with the "COMMIT_WMAP" flag, preventing modifications in "read-only" mode.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local, low-privileged user may trigger unsafe JFS truncation behavior when the filesystem is read-only. The flaw can attempt a transaction without an available journal log, potentially affecting confidentiality, integrity, and availability. Systems not using JFS, or without relevant local access, are less exposed.

Executive priority

Prioritize internet-facing multi-user hosts, shared compute, and systems processing untrusted storage. The local-access and JFS prerequisites reduce broad exposure, but the stated high confidentiality, integrity, and availability impact supports prompt patching where both conditions exist.

Technical view

The Linux JFS write-failure path could reach jfs_truncate_nolock() on a read-only filesystem and continue into txEnd() with a null log pointer. The correction adds a read-only check and invokes xtTruncate with COMMIT_WMAP, stopping further data modification. CVSS 3.1 is 7.8: local access, low complexity, low privileges, and no user interaction.

Likely exposure

Exposure requires a Linux system using JFS and a local, low-privileged attack path. The supplied record marks Linux versions using boundaries including 2.6.12, 6.14.2, and 6.15, but does not clearly express every fixed release. Confirm status against the running distribution kernel.

Exploitation context

The supplied sources do not report active exploitation, and the CVE is not listed as KEV in the bundle. The CVSS vector describes a local, low-complexity condition requiring low privileges. Evidence provided does not establish remote exploitation or a public exploit.

Researcher notes

The supplied description identifies a null JFS log within the truncation transaction path, but does not document the demonstrated failure mode, exploit reliability, or affected-version ranges unambiguously. Treat the cited stable commits and distribution backport status as authoritative validation points; do not infer safety from kernel version alone.

Mitigation direction

  • Install a vendor-supported kernel containing the cited JFS correction.
  • Check distribution advisories for the exact fixed kernel release.
  • Restrict untrusted local access until affected systems are updated.
  • Avoid mounting untrusted JFS filesystems where operationally practical.

Validation and detection

  • Record each system's kernel and distribution package versions.
  • Identify hosts mounting or capable of mounting JFS filesystems.
  • Compare installed kernels with vendor advisories and cited stable commits.
  • Confirm the deployed source includes the read-only check in jfs_truncate_nolock().
  • Reboot updated systems and verify the new kernel is active.
Prepared
Confidence
medium
Sources
4

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-58094 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
0ADP providers
3Source links

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-58094Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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