CVE-2024-58095: jfs: add check read-only before txBeginAnon() call
In the Linux kernel, the following vulnerability has been resolved:
jfs: add check read-only before txBeginAnon() call
Added a read-only check before calling `txBeginAnon` in `extAlloc`
and `extRecord`. This prevents modification attempts on a read-only
mounted filesystem, avoiding potential errors or crashes.
Call trace:
txBeginAnon+0xac/0x154
extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78
jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248
__block_write_begin_int+0x580/0x166c fs/buffer.c:2128
__block_write_begin fs/buffer.c:2177 [inline]
block_write_begin+0x98/0x11c fs/buffer.c:2236
jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299
Security readout for executives and security teams
Plain-English summary
This Linux kernel JFS issue can let a read-only mounted filesystem still reach transaction-modifying code, creating potential errors or crashes. It matters mainly where JFS is in use, especially legacy or specialized Linux hosts. The public record does not provide CVSS, CWE, or confirmed exploit activity.
Executive priority
Treat as a focused Linux hardening item, not an emergency based on current evidence. Prioritize affected JFS-using systems during normal kernel patch cycles unless business-critical hosts rely on JFS.
Technical view
The fix adds read-only checks before txBeginAnon() in JFS extAlloc and extRecord. The reported trace passes through jfs_get_block and jfs_write_begin, indicating a write-path transaction attempt on a read-only mount. Public sources describe crash avoidance, not privilege escalation or data theft.
Likely exposure
Exposure appears limited to Linux systems with JFS enabled and mounted, particularly read-only JFS filesystems. The source lists Linux kernel version data but not distro-specific package versions or backport status.
Exploitation context
CISA KEV is false in the provided bundle, and no cited source claims active exploitation. The public evidence is a kernel vulnerability record and stable commits. Trigger prerequisites are not fully documented.
Researcher notes
Evidence supports a JFS read-only state check flaw leading to errors or crashes. Severity, exploitability, and exact affected distro builds are incomplete in the bundle. Avoid expanding impact beyond the stated crash/error prevention.
Mitigation direction
Check Linux vendor advisories for kernel packages containing the referenced JFS fix.
Prioritize updates on systems that mount JFS filesystems, especially read-only mounts.
If patching is delayed, reduce or retire JFS usage where operationally feasible.
Track distribution backports instead of relying only on upstream kernel version numbers.
Validation and detection
Inventory hosts with JFS support loaded or JFS filesystems mounted.
Compare running kernel packages against vendor advisories for CVE-2024-58095.
Review filesystem configurations for read-only JFS mounts.
Confirm the referenced upstream stable commits are present or backported.
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-58095 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:11 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.