jfs_truncate_nolock() · jfs: add check read-only before truncation
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 29 Oct 2026, 22:53 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
Description
CVE-2024-58094 relates to a vulnerability in the jfs_truncate_nolock() function where a check for read-only status before truncation was added. The description and details are minimal, and no specific impact or exploitation details are provided.