ocfs2: prevent release journal inode after journal shutdown
Summary
| CVE | CVE-2025-39842 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-09-19 16:15:42 UTC |
| Updated | 2026-05-12 13:17:15 UTC |
| Description | 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. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: NVD-CWE-noinfo
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 42c415c53ad2065088cc411d08925effa5b3d255 git | Not specified |
| CNA | Linux | Linux | affected da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 e9188f66e94955431ddbe2cd1cdf8ff2bb486abf git | Not specified |
| CNA | Linux | Linux | affected da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 f4a917e6cd6c798f7adf39907f117fc754db1283 git | Not specified |
| CNA | Linux | Linux | affected da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 85e66331b60601d903cceaf8c10a234db863cd78 git | Not specified |
| CNA | Linux | Linux | affected da5e7c87827e8caa6a1eeec6d95dcf74ab592a01 f46e8ef8bb7b452584f2e75337b619ac51a7cadf git | Not specified |
| CNA | Linux | Linux | affected 5.16 | Not specified |
| CNA | Linux | Linux | unaffected 5.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.151 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.105 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.46 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.16.6 6.16.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.17 * original_commit_for_fix | Not specified |
| ADP | Siemens | SIMATIC CN 4100 | affected V5.0 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| lists.debian.org/debian-lts-announce/2025/10/msg00008.html | af854a3a-2127-422b-91ae-364da2661108 | lists.debian.org | Mailing List, Third Party Advisory |
| git.kernel.org/stable/c/f46e8ef8bb7b452584f2e75337b619ac51a7cadf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/42c415c53ad2065088cc411d08925effa5b3d255 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/e9188f66e94955431ddbe2cd1cdf8ff2bb486abf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/f4a917e6cd6c798f7adf39907f117fc754db1283 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| cert-portal.siemens.com/productcert/html/ssa-032379.html | 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e | cert-portal.siemens.com | |
| git.kernel.org/stable/c/85e66331b60601d903cceaf8c10a234db863cd78 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.