# CVE-2024-58095: jfs: add check read-only before txBeginAnon() call

> A missing read-only check in the Linux kernel JFS filesystem allows attackers to cause a crash or system instability by attempting write operations on a read-only mounted volume.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2025
- **Updated:** 2 Sep 2026
- **Also known as:** BELL-CVE-2024-58095, DEBIAN-CVE-2024-58095, GHSA-cxcw-75qj-r943, ROOT-OS-DEBIAN-11-CVE-2024-58095, ROOT-OS-DEBIAN-12-CVE-2024-58095, ROOT-OS-DEBIAN-13-CVE-2024-58095, ROOT-OS-UBUNTU-2204-CVE-2024-58095, ROOT-OS-UBUNTU-2404-CVE-2024-58095, UBUNTU-CVE-2024-58095

## What is CVE-2024-58095?

CVE-2024-58095 is a medium-severity denial of service vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

## Which versions are affected by CVE-2024-58095?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-58095?

Apply the vendor's patch.

## Is CVE-2024-58095 being exploited?

There is no known exploitation of CVE-2024-58095 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58095 and fix it if it is affected.

What it is: CVE-2024-58095 is a medium-severity denial of service vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58095 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58095/ (Markdown: https://insights.sbomify.com/CVE-2024-58095/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58095
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58095
- OSV: https://osv.dev/vulnerability/CVE-2024-58095

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58095/
Summaries are generated and may contain mistakes; the official description above is the record.