CVE-2025-39842: ocfs2: prevent release journal inode after journal shutdown
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.17% (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 42c415c53ad2065088cc411d08925effa5b3d255, 85e66331b60601d903cceaf8c10a234db863cd78, e9188f66e94955431ddbe2cd1cdf8ff2bb486abf; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 42c415c53ad2065088cc411d08925effa5b3d255, 85e66331b60601d903cceaf8c10a234db863cd78, e9188f66e94955431ddbe2cd1cdf8ff2bb486abf; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 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: ocfs2: prevent release journal inode after journal shutdown Before calling ocfs2_delete_osb(), ocfs2_journal_shutdown() has already been executed in ocfs2_dismount_volume(), so osb->journal must be NULL. Therefore, the following calltrace will inevitably fail when it reaches jbd2_journal_release_jbd_inode(). ocfs2_dismount_volume()-> ocfs2_delete_osb()-> ocfs2_free_slot_info()-> __ocfs2_free_slot_info()-> evict()-> ocfs2_evict_inode()-> ocfs2_clear_inode()-> jbd2_journal_release_jbd_inode(osb->journal->j_journal, Adding osb->journal checks will prevent null-ptr-deref during the above execution path.
- Published
- Sep 19, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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.1%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.16 and later · before 6.1.151
- linux linux kernel6.2 and later · before 6.6.105
- linux linux kernel6.7 and later · before 6.12.46
- linux linux kernel6.13 and later · before 6.16.6
- linux linux kernel6.17
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
- 5.16affected
- da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 and later · before 42c415c53ad2065088cc411d08925effa5b3d255affected · git
- da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 and later · before e9188f66e94955431ddbe2cd1cdf8ff2bb486abfaffected · git
- da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 and later · before f4a917e6cd6c798f7adf39907f117fc754db1283affected · git
- da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 and later · before 85e66331b60601d903cceaf8c10a234db863cd78affected · git
- da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 and later · before f46e8ef8bb7b452584f2e75337b619ac51a7cadfaffected · git
- before 5.16not affected · semver
- 6.1.151 and later · up to and including 6.1.*not affected · semver
- 6.6.105 and later · up to and including 6.6.*not affected · semver
- 6.12.46 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.48-1 | 6.12.48-1 |
| Debian:14 | linux | before 6.16.6-1 | 6.16.6-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-2025-39840Sep 19, 2025 · audit: fix out-of-bounds read in audit_compare_dname_path()28Monitor
- ← EarlierCVE-2025-39841Sep 19, 2025 · scsi: lpfc: Fix buffer free/clear order in deferred receive path31Monitor
- Later →CVE-2025-39843Sep 19, 2025 · mm: slub: avoid wake up kswapd in set_track_prepare22Monitor
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 | 42c415c53ad2065088cc411d08925effa5b3d255 | Vendor (CNA) |
| Linux Linux | 85e66331b60601d903cceaf8c10a234db863cd78 | Vendor (CNA) |
| Linux Linux | e9188f66e94955431ddbe2cd1cdf8ff2bb486abf | Vendor (CNA) |
| Linux Linux | f46e8ef8bb7b452584f2e75337b619ac51a7cadf | Vendor (CNA) |
| Linux Linux | f4a917e6cd6c798f7adf39907f117fc754db1283 | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.153-1 · Debian:12 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/85e66331b60601d903cceaf8c10a234db863cd78
- git.kernel.org/stable/c/e9188f66e94955431ddbe2cd1cdf8ff2bb486abf
- git.kernel.org/stable/c/f46e8ef8bb7b452584f2e75337b619ac51a7cadf
- git.kernel.org/stable/c/f4a917e6cd6c798f7adf39907f117fc754db1283
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-032379.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.