CVE-2025-37925: jfs: reject on-disk inodes of an unsupported type
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 28419a4f3a1eeee33472a1b3856ae62aaa5a649b, 45fd8421081ec79e661e5f3ead2934fdbddb4287, 8987891c4653874d5e3f5d11f063912f4e0b58eb.
Low priority for now. Upgrade to Linux Linux 28419a4f3a1eeee33472a1b3856ae62aaa5a649b, 45fd8421081ec79e661e5f3ead2934fdbddb4287, 8987891c4653874d5e3f5d11f063912f4e0b58eb or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: jfs: reject on-disk inodes of an unsupported type Syzbot has reported the following BUG: kernel BUG at fs/inode.c:668! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 3 UID: 0 PID: 139 Comm: jfsCommit Not tainted 6.12.0-rc4-syzkaller-00085-g4e46774408d9 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014 RIP: 0010:clear_inode+0x168/0x190 Code: 4c 89 f7 e8 ba fe e5 ff e9 61 ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 7c c1 4c 89 f7 e8 90 ff e5 ff eb b7 0b e8 01 5d 7f ff 90 0f 0b e8 f9 5c 7f ff 90 0f 0b e8 f1 5c 7f RSP: 0018:ffffc900027dfae8 EFLAGS: 00010093 RAX: ffffffff82157a87 RBX: 0000000000000001 RCX: ffff888104d4b980 RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000 RBP: ffffc900027dfc90 R08: ffffffff82157977 R09: fffff520004fbf38 R10: dffffc0000000000 R11: fffff520004fbf38 R12: dffffc0000000000 R13: ffff88811315bc00 R14: ffff88811315bda8 R15: ffff88811315bb80 FS: 0000000000000000(0000) GS:ffff888135f00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005565222e0578 CR3: 0000000026ef0000 CR4: 00000000000006f0 Call Trace: <TASK> ? __die_body+0x5f/0xb0 ? die+0x9e/0xc0 ? do_trap+0x15a/0x3a0 ? clear_inode+0x168/0x190 ? do_error_trap+0x1dc/0x2c0 ? clear_inode+0x168/0x190 ? __pfx_do_error_trap+0x10/0x10 ? report_bug+0x3cd/0x500 ? handle_invalid_op+0x34/0x40 ? clear_inode+0x168/0x190 ? exc_invalid_op+0x38/0x50 ? asm_exc_invalid_op+0x1a/0x20 ? clear_inode+0x57/0x190 ? clear_inode+0x167/0x190 ? clear_inode+0x168/0x190 ? clear_inode+0x167/0x190 jfs_evict_inode+0xb5/0x440 ? __pfx_jfs_evict_inode+0x10/0x10 evict+0x4ea/0x9b0 ? __pfx_evict+0x10/0x10 ? iput+0x713/0xa50 txUpdateMap+0x931/0xb10 ? __pfx_txUpdateMap+0x10/0x10 jfs_lazycommit+0x49a/0xb80 ? _raw_spin_unlock_irqrestore+0x8f/0x140 ? lockdep_hardirqs_on+0x99/0x150 ? __pfx_jfs_lazycommit+0x10/0x10 ? __pfx_default_wake_function+0x10/0x10 ? __kthread_parkme+0x169/0x1d0 ? __pfx_jfs_lazycommit+0x10/0x10 kthread+0x2f2/0x390 ? __pfx_jfs_lazycommit+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x4d/0x80 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> This happens when 'clear_inode()' makes an attempt to finalize an underlying JFS inode of unknown type. According to JFS layout description from https://jfs.sourceforge.net/project/pub/jfslayout.pdf, inode types from 5 to 15 are reserved for future extensions and should not be encountered on a valid filesystem. So add an extra check for valid inode type in 'copy_from_dinode()'.
- Published
- Apr 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.1affected
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before fa6ce4a9cc9fcc8150b80db6f65186c0ed2b3143affected · git
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before afc08b0b5587b553799bc375957706936a3e0088affected · git
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before 45fd8421081ec79e661e5f3ead2934fdbddb4287affected · git
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before 28419a4f3a1eeee33472a1b3856ae62aaa5a649baffected · git
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before 8987891c4653874d5e3f5d11f063912f4e0b58ebaffected · git
- 79ac5a46c5c1c17476fbf84b4d4600d6d565defd and later · before 8c3f9a70d2d4dd6c640afe294b05c6a0a45434d9affected · git
- before 3.1not affected · semver
- 5.15.190 and later · up to and including 5.15.*not affected · semver
- 6.1.148 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.1 and later · before 5.15.190
- linux linux kernel5.16 and later · before 6.1.148
- linux linux kernel6.2 and later · before 6.6.101
- linux linux kernel6.7 and later · before 6.12.41
- linux linux kernel6.13 and later · before 6.14.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux-6.1 | before 6.1.153-1~deb11u1 | 6.1.153-1~deb11u1 |
| Debian:12 | linux | before 6.1.148-1 | 6.1.148-1 |
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47671Apr 17, 2025 · can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path13Monitor
- ← EarlierCVE-2025-37893Apr 18, 2025 · LoongArch: BPF: Fix off-by-one error in build_prologue()22Monitor
- Later →CVE-2025-38049Apr 18, 2025 · x86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 28419a4f3a1eeee33472a1b3856ae62aaa5a649b | Vendor (CNA) |
| Linux Linux | 45fd8421081ec79e661e5f3ead2934fdbddb4287 | Vendor (CNA) |
| Linux Linux | 8987891c4653874d5e3f5d11f063912f4e0b58eb | Vendor (CNA) |
| Linux Linux | 8c3f9a70d2d4dd6c640afe294b05c6a0a45434d9 | Vendor (CNA) |
| Linux Linux | afc08b0b5587b553799bc375957706936a3e0088 | Vendor (CNA) |
| Linux Linux | fa6ce4a9cc9fcc8150b80db6f65186c0ed2b3143 | Vendor (CNA) |
| debian:linux | 6.1.148-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.153-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/45fd8421081ec79e661e5f3ead2934fdbddb4287
- git.kernel.org/stable/c/8987891c4653874d5e3f5d11f063912f4e0b58eb
- git.kernel.org/stable/c/8c3f9a70d2d4dd6c640afe294b05c6a0a45434d9
- git.kernel.org/stable/c/afc08b0b5587b553799bc375957706936a3e0088
- git.kernel.org/stable/c/fa6ce4a9cc9fcc8150b80db6f65186c0ed2b3143
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.