BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-39885High confidence

ocfs2: fix recursive semaphore deadlock in fiemap call

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.48-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-39885 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2025-39885
352 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP3
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix recursive semaphore deadlock in fiemap call syzbot detected a OCFS2 hang due to a recursive semaphore on a FS_IOC_FIEMAP of the extent list on a specially crafted mmap file. context_switch kernel/sched/core.c:5357 [inline] __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961 __schedule_loop kernel/sched/core.c:7043 [inline] schedule+0x165/0x360 kernel/sched/core.c:7058 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7115 rwsem_down_write_slowpath+0x872/0xfe0 kernel/locking/rwsem.c:1185 __down_write_common kernel/locking/rwsem.c:1317 [inline] __down_write kernel/locking/rwsem.c:1326 [inline] down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1591 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14d/0x310 mm/memory.c:3361 wp_page_shared mm/memory.c:3762 [inline] do_wp_page+0x268d/0x5800 mm/memory.c:3981 handle_pte_fault mm/memory.c:6068 [inline] __handle_mm_fault+0x1033/0x5440 mm/memory.c:6195 handle_mm_fault+0x40a/0x8e0 mm/memory.c:6364 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline] RIP: 0010:raw_copy_to_user arch/x86/include/asm/uaccess_64.h:147 [inline] RIP: 0010:_inline_copy_to_user include/linux/uaccess.h:197 [inline] RIP: 0010:_copy_to_user+0x85/0xb0 lib/usercopy.c:26 Code: e8 00 bc f7 fc 4d 39 fc 72 3d 4d 39 ec 77 38 e8 91 b9 f7 fc 4c 89 f7 89 de e8 47 25 5b fd 0f 01 cb 4c 89 ff 48 89 d9 4c 89 f6 a4 0f 1f 00 48 89 cb 0f 01 ca 48 89 d8 5b 41 5c 41 5d 41 5e 41 RSP: 0018:ffffc9000403f950 EFLAGS: 00050256 RAX: ffffffff84c7f101 RBX: 0000000000000038 RCX: 0000000000000038 RDX: 0000000000000000 RSI: ffffc9000403f9e0 RDI: 0000200000000060 RBP: ffffc9000403fa90 R08: ffffc9000403fa17 R09: 1ffff92000807f42 R10: dffffc0000000000 R11: fffff52000807f43 R12: 0000200000000098 R13: 00007ffffffff000 R14: ffffc9000403f9e0 R15: 0000200000000060 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ocfs2_fiemap+0x888/0xc90 fs/ocfs2/extent_map.c:806 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1173/0x1430 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f5f13850fd9 RSP: 002b:00007ffe3b3518b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000200000000000 RCX: 00007f5f13850fd9 RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000004 RBP: 6165627472616568 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3b3518f0 R13: 00007ffe3b351b18 R14: 431bde82d7b634db R15: 00007f5f1389a03b ocfs2_fiemap() takes a read lock of the ip_alloc_sem semaphore (since v2.6.22-527-g7307de80510a) and calls fiemap_fill_next_extent() to read the extent list of this running mmap executable. The user supplied buffer to hold the fiemap information page faults calling ocfs2_page_mkwrite() which will take a write lock (since v2.6.27-38-g00dc417fa3e7) of the same semaphore. This recursive semaphore will hold filesystem locks and causes a hang of the fileystem. The ip_alloc_sem protects the inode extent list and size. Release the read semphore before calling fiemap_fill_next_extent() in ocfs2_fiemap() and ocfs2_fiemap_inline(). This does an unnecessary semaphore lock/unlock on the last extent but simplifies the error path.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-30849

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix recursive semaphore deadlock in fiemap call syzbot detected a OCFS2 hang due to a recursive semaphore on a FS_IOC_FIEMAP of the extent list on a specially crafted mmap file. context_switch kernel/sched/core.c:5357 [inline] __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961 __schedule_loop kernel/sched/core.c:7043 [inline] schedule+0x165/0x360 kernel/sched/core.c:7058 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7115 rwsem_down_write_slowpath+0x872/0xfe0 kernel/locking/rwsem.c:1185 __down_write_common kernel/locking/rwsem.c:1317 [inline] __down_write kernel/locking/rwsem.c:1326 [inline] down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1591 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14d/0x310 mm/memory.c:3361 wp_page_shared mm/memory.c:3762 [inline] do_wp_page+0x268d/0x5800 mm/memory.c:3981 handle_pte_fault mm/memory.c:6068 [inline] __handle_mm_fault+0x1033/0x5440 mm/memory.c:6195 handle_mm_fault+0x40a/0x8e0 mm/memory.c:6364 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline] RIP: 0010:raw_copy_to_user arch/x86/include/asm/uaccess_64.h:147 [inline] RIP: 0010:_inline_copy_to_user include/linux/uaccess.h:197 [inline] RIP: 0010:_copy_to_user+0x85/0xb0 lib/usercopy.c:26 Code: e8 00 bc f7 fc 4d 39 fc 72 3d 4d 39 ec 77 38 e8 91 b9 f7 fc 4c 89 f7 89 de e8 47 25 5b fd 0f 01 cb 4c 89 ff 48 89 d9 4c 89 f6 <f3> a4 0f 1f 00 48 89 cb 0f 01 ca 48 89 d8 5b 41 5c 41 5d 41 5e 41 RSP: 0018:ffffc9000403f950 EFLAGS: 00050256 RAX: ffffffff84c7f101 RBX: 0000000000000038 RCX: 0000000000000038 RDX: 0000000000000000 RSI: ffffc9000403f9e0 RDI: 0000200000000060 RBP: ffffc9000403fa90 R08: ffffc9000403fa17 R09: 1ffff92000807f42 R10: dffffc0000000000 R11: fffff52000807f43 R12: 0000200000000098 R13: 00007ffffffff000 R14: ffffc9000403f9e0 R15: 0000200000000060 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ocfs2_fiemap+0x888/0xc90 fs/ocfs2/extent_map.c:806 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1173/0x1430 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f5f13850fd9 RSP: 002b:00007ffe3b3518b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000200000000000 RCX: 00007f5f13850fd9 RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000004 RBP: 6165627472616568 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3b3518f0 R13: 00007ffe3b351b18 R14: 431bde82d7b634db R15: 00007f5f1389a03b ocfs2_fiemap() takes a read lock of the ip_alloc_sem semaphore (since v2.6.22-527-g7307de80510a) and calls fiemap_fill_next_extent() to read the extent list of this running mmap executable. The user supplied buffer to hold the fiemap information page faults calling ocfs2_page_mkwrite() which will take a write lock (since v2.6.27-38-g00dc417fa3e7) of the same semaphore. This recursive semaphore will hold filesystem locks and causes a hang of the fileystem. The ip_alloc_sem protects the inode extent list and size. Release the read semphore before calling fiemap_fill_next_extent() in ocfs2_fiemap() and ocfs2_fiemap_inline(). This does an unnecessary semaphore lock/unlock on the last extent but simplifies the error path.

What

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix recursive semaphore deadlock in fiemap call syzbot detected a OCFS2 hang due to a recursive semaphore on a FS_IOC_FIEMAP of the extent list on a specially crafted mmap file. context_switch kernel/sched/core.c:5357 [inline] __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961 __schedule_loop kernel/sched/core.c:7043 [inline] schedule+0x165/0x360 kernel/sched/core.c:7058 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7115 rwsem_down_write_slowpath+0x872/0xfe0 kernel/locking/rwsem.c:1185 __down_write_common kernel/locking/rwsem.c:1317 [inline] __down_write kernel/locking/rwsem.c:1326 [inline] down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1591 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14d/0x310 mm/memory.c:3361 wp_page_shared mm/memory.c:3762 [inline] do_wp_page+0x268d/0x5800 mm/memory.c:3981 handle_pte_fault mm/memory.c:6068 [inline] __handle_mm_fault+0x1033/0x5440 mm/memory.c:6195 handle_mm_fault+0x40a/0x8e0 mm/memory.c:6364 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline] RIP: 0010:raw_copy_to_user arch/x86/include/asm/uaccess_64.h:147 [inline] RIP: 0010:_inline_copy_to_user include/linux/uaccess.h:197 [inline] RIP: 0010:_copy_to_user+0x85/0xb0 lib/usercopy.c:26 Code: e8 00 bc f7 fc 4d 39 fc 72 3d 4d 39 ec 77 38 e8 91 b9 f7 fc 4c 89 f7 89 de e8 47 25 5b fd 0f 01 cb 4c 89 ff 48 89 d9 4c 89 f6 <f3> a4 0f 1f 00 48 89 cb 0f 01 ca 48 89 d8 5b 41 5c 41 5d 41 5e 41 RSP: 0018:ffffc9000403f950 EFLAGS: 00050256 RAX: ffffffff84c7f101 RBX: 0000000000000038 RCX: 0000000000000038 RDX: 0000000000000000 RSI: ffffc9000403f9e0 RDI: 0000200000000060 RBP: ffffc9000403fa90 R08: ffffc9000403fa17 R09: 1ffff92000807f42 R10: dffffc0000000000 R11: fffff52000807f43 R12: 0000200000000098 R13: 00007ffffffff000 R14: ffffc9000403f9e0 R15: 0000200000000060 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ocfs2_fiemap+0x888/0xc90 fs/ocfs2/extent_map.c:806 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1173/0x1430 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f5f13850fd9 RSP: 002b:00007ffe3b3518b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000200000000000 RCX: 00007f5f13850fd9 RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000004 RBP: 6165627472616568 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3b3518f0 R13: 00007ffe3b351b18 R14: 431bde82d7b634db R15: 00007f5f1389a03b ocfs2_fiemap() takes a read lock of the ip_alloc_sem semaphore (since v2.6.22-527-g7307de80510a) and calls fiemap_fill_next_extent() to read the extent list of this running mmap executable. The user supplied buffer to hold the fiemap information page faults calling ocfs2_page_mkwrite() which will take a write lock (since v2.6.27-38-g00dc417fa3e7) of the same semaphore. This recursive semaphore will hold filesystem locks and causes a hang of the fileystem. The ip_alloc_sem protects the inode extent list and size. Release the read semphore before calling fiemap_fill_next_extent() in ocfs2_fiemap() and ocfs2_fiemap_inline(). This does an unnecessary semaphore lock/unlock on the last extent but simplifies the error path.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix recursive semaphore deadlock in fiemap call syzbot detected a OCFS2 hang due to a recursive semaphore on a FS_IOC_FIEMAP of the extent list on a specially crafted mmap file. context_switch kernel/sched/core.c:5357 [inline] __schedule+0x1798/0x4cc0 kernel/sched/core.c:6961 __schedule_loop kernel/sched/core.c:7043 [inline] schedule+0x165/0x360 kernel/sched/core.c:7058 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7115 rwsem_down_write_slowpath+0x872/0xfe0 kernel/locking/rwsem.c:1185 __down_write_common kernel/locking/rwsem.c:1317 [inline] __down_write kernel/locking/rwsem.c:1326 [inline] down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1591 ocfs2_page_mkwrite+0x2ff/0xc40 fs/ocfs2/mmap.c:142 do_page_mkwrite+0x14d/0x310 mm/memory.c:3361 wp_page_shared mm/memory.c:3762 [inline] do_wp_page+0x268d/0x5800 mm/memory.c:3981 handle_pte_fault mm/memory.c:6068 [inline] __handle_mm_fault+0x1033/0x5440 mm/memory.c:6195 handle_mm_fault+0x40a/0x8e0 mm/memory.c:6364 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline] RIP: 0010:raw_copy_to_user arch/x86/include/asm/uaccess_64.h:147 [inline] RIP: 0010:_inline_copy_to_user include/linux/uaccess.h:197 [inline] RIP: 0010:_copy_to_user+0x85/0xb0 lib/usercopy.c:26 Code: e8 00 bc f7 fc 4d 39 fc 72 3d 4d 39 ec 77 38 e8 91 b9 f7 fc 4c 89 f7 89 de e8 47 25 5b fd 0f 01 cb 4c 89 ff 48 89 d9 4c 89 f6 <f3> a4 0f 1f 00 48 89 cb 0f 01 ca 48 89 d8 5b 41 5c 41 5d 41 5e 41 RSP: 0018:ffffc9000403f950 EFLAGS: 00050256 RAX: ffffffff84c7f101 RBX: 0000000000000038 RCX: 0000000000000038 RDX: 0000000000000000 RSI: ffffc9000403f9e0 RDI: 0000200000000060 RBP: ffffc9000403fa90 R08: ffffc9000403fa17 R09: 1ffff92000807f42 R10: dffffc0000000000 R11: fffff52000807f43 R12: 0000200000000098 R13: 00007ffffffff000 R14: ffffc9000403f9e0 R15: 0000200000000060 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ocfs2_fiemap+0x888/0xc90 fs/ocfs2/extent_map.c:806 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1173/0x1430 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f5f13850fd9 RSP: 002b:00007ffe3b3518b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000200000000000 RCX: 00007f5f13850fd9 RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000004 RBP: 6165627472616568 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe3b3518f0 R13: 00007ffe3b351b18 R14: 431bde82d7b634db R15: 00007f5f1389a03b ocfs2_fiemap() takes a read lock of the ip_alloc_sem semaphore (since v2.6.22-527-g7307de80510a) and calls fiemap_fill_next_extent() to read the extent list of this running mmap executable. The user supplied buffer to hold the fiemap information page faults calling ocfs2_page_mkwrite() which will take a write lock (since v2.6.27-38-g00dc417fa3e7) of the same semaphore. This recursive semaphore will hold filesystem locks and causes a hang of the fileystem. The ip_alloc_sem protects the inode extent list and size. Release the read semphore before calling fiemap_fill_next_extent() in ocfs2_fiemap() and ocfs2_fiemap_inline(). This does an unnecessary semaphore lock/unlock on the last extent but simplifies the error path.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2025-2107Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250924Security Bulletin 24 Sep 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 24 Sep 2025, published on 24 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0602Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39886 https://www.cve.org/CVERecord?id=CVE-2025-39886 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0545Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-38408 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39945 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0453Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-38408 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-38591 https://www.cve.org/CVERecord?id=CVE-2025-38591 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39945 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0421Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39886 https://www.cve.org/CVERecord?id=CVE-2025-39886 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39897 https://www.cve.org/CVERecord?id=CVE-2025-39897 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0397Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39886 https://www.cve.org/CVERecord?id=CVE-2025-39886 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39897 https://www.cve.org/CVERecord?id=CVE-2025-39897 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0371Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39886 https://www.cve.org/CVERecord?id=CVE-2025-39886 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39897 https://www.cve.org/CVERecord?id=CVE-2025-39897 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0331Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39886 https://www.cve.org/CVERecord?id=CVE-2025-39886 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39897 https://www.cve.org/CVERecord?id=CVE-2025-39897 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0209Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-38236 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39945 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-38236 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39943 https://www.cve.org/CVERecord?id=CVE-2025-39943 Référence CVE CVE-2025-39945 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0194Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0169Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 https://www.cve.org/CVERecord?id=CVE-2025-39801 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39934 https://www.cve.org/CVERecord?id=CVE-2025-39934 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1136Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-21861 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-38678 https://www.cve.org/CVERecord?id=CVE-2025-38678 Référence CVE CVE-2025-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39937 https://www.cve.org/CVERecord?id=CVE-2025-39937 Référence CVE CVE-2025-39945 https://www.cve.org/CVERecord?id=CVE-2025-39945 Référence CVE CVE-2025-39949 https://www.cve.org/CVERecord?id=CVE-2025-39949 Référence CVE CVE-2025-39951 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39875 https://www.cve.org/CVERecord?id=CVE-2025-39875 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39882 https://www.cve.org/CVERecord?id=CVE-2025-39882 Référence CVE CVE-2025-39884 https://www.cve.org/CVERecord?id=CVE-2025-39884 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 Référence CVE CVE-2025-39896 https://www.cve.org/CVERecord?id=CVE-2025-39896 Référence CVE CVE-2025-39898 https://www.cve.org/CVERecord?id=CVE-2025-39898 Référence CVE CVE-2025-39899 https://www.cve.org/CVERecord?id=CVE-2025-39899 Référence CVE CVE-2025-39900 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39861 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-39864 https://www.cve.org/CVERecord?id=CVE-2025-39864 Référence CVE CVE-2025-39865 https://www.cve.org/CVERecord?id=CVE-2025-39865 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39882 https://www.cve.org/CVERecord?id=CVE-2025-39882 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39920 https://www.cve.org/CVERecord?id=CVE-2025-39920 Référence CVE CVE-2025-39922 https://www.cve.org/CVERecord?id=CVE-2025-39922 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-39861 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-39864 https://www.cve.org/CVERecord?id=CVE-2025-39864 Référence CVE CVE-2025-39865 https://www.cve.org/CVERecord?id=CVE-2025-39865 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39871 https://www.cve.org/CVERecord?id=CVE-2025-39871 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39882 https://www.cve.org/CVERecord?id=CVE-2025-39882 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39889 https://www.cve.org/CVERecord?id=CVE-2025-39889 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39920 https://www.cve.org/CVERecord?id=CVE-2025-39920 Référence CVE CVE-2025-39922 https://www.cve.org/CVERecord?id=CVE-2025-39922 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0894Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-39866 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39870 https://www.cve.org/CVERecord?id=CVE-2025-39870 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39877 https://www.cve.org/CVERecord?id=CVE-2025-39877 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39883 https://www.cve.org/CVERecord?id=CVE-2025-39883 Référence CVE CVE-2025-39885 https://www.cve.org/CVERecord?id=CVE-2025-39885 Référence CVE CVE-2025-39891 https://www.cve.org/CVERecord?id=CVE-2025-39891 Référence CVE CVE-2025-39894 https://www.cve.org/CVERecord?id=CVE-2025-39894 Référence CVE CVE-2025-39898 https://www.cve.org/CVERecord?id=CVE-2025-39898 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-39907 https://www.cve.org/CVERecord?id=CVE-2025-39907 Référence CVE CVE-2025-39909 https://www.cve.org/CVERecord?id=CVE-2025-39909 Référence CVE CVE-2025-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-024942Debian等の複数ベンダの製品におけるリソースのロックに関する脆弱性

Linuxカーネルにおいて、ocfs2ファイルシステムのfiemapコール内で再帰的なセマフォデッドロックが発生し、ファイルシステムがハングする脆弱性が修正されました。この問題は、拡張情報リストの読み取り時にリードロックを取得し、ページフォルト処理で同じセマフォのライトロックを取得することで発生していました。修正では、fiemap_fill_next_extent()呼び出し前にリードセマフォを解放するように変更され、再帰的なロックを防止しています。これにより、OCFS2がファイルシステムのハングを引き起こす問題が解消されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.28, 5.4.300 ≤ 5.4.*, 5.10.245 ≤ 5.10.*, 5.15.194 ≤ 5.15.*, 6.1.153 ≤ 6.1.*, 6.6.107 ≤ 6.6.*, 6.12.48 ≤ 6.12.*, 6.16.8 ≤ 6.16.*, 6.17 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 23 Sept 2025 · Last source change 11 May 2026, 21:38 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-30849
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-39885 · cve.blacktree.nl