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

fs: writeback: fix use-after-free in __mark_inode_dirty()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 32 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.31% 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: As exposure requiresRemediation target: Within 365 days

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 32 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.153-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.16.6-1Debian Security Tracker ↗Source updated 5 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.

4 current
CVE-2025-39866 · CSAF 2.0 · revision 56 · interimSUSE Product Security TeamCVE-2025-39866
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: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

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

  • SIMATIC CN 4100
Summary
In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.
Remediation
Update to V5.0 or later version
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-30334

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

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
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 32 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: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

What

In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-30334Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: fs: writeback: fix use-after-free in __mark_inode_dirty() An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching. CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198 Root cause is: systemd-random-seed kworker ---------------------------------------------------------------------- ___mark_inode_dirty inode_switch_wbs_work_fn spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
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-2099Linux 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-0880Multiples vulnérabilités dans les produits Siemens

25-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2025-39846 Référence CVE CVE-2025-39847 https://www.cve.org/CVERecord?id=CVE-2025-39847 Référence CVE CVE-2025-39848 https://www.cve.org/CVERecord?id=CVE-2025-39848 Référence CVE CVE-2025-39849 https://www.cve.org/CVERecord?id=CVE-2025-39849 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 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-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 Référence CVE CVE-2025-40300 https://www.cve.org/CVERecord?id=CVE-2025-40300 Référence CVE CVE-2025-40833 https://www.cve.org/CVERecord?id=CVE-2025-40833 Référence CVE CVE-2025-43368 https://www.cve.org/CVERecord?id=CVE-2025-43368 Référence CVE CVE-2025-47219 https://www.cve.org/CVERecord?id=CVE-2025-47219 Référence CVE CVE-2025-48989 https://www.cve.org/CVERecord?id=CVE-2025-48989 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-55752 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-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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=

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

d?id=CVE-2025-39844 Référence CVE CVE-2025-39845 https://www.cve.org/CVERecord?id=CVE-2025-39845 Référence CVE CVE-2025-39846 https://www.cve.org/CVERecord?id=CVE-2025-39846 Référence CVE CVE-2025-39847 https://www.cve.org/CVERecord?id=CVE-2025-39847 Référence CVE CVE-2025-39848 https://www.cve.org/CVERecord?id=CVE-2025-39848 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 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-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 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-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-39920 https://www.cve.org/CVERecord?id=CVE-2025-39920 Référence CVE CVE-2025-39946 https://www.cve.org/CVERecord?id=CVE-2025-39946 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-40018 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-2023-53498 Référence CVE CVE-2024-47666 https://www.cve.org/CVERecord?id=CVE-2024-47666 Référence CVE CVE-2024-50143 https://www.cve.org/CVERecord?id=CVE-2024-50143 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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-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=

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

d?id=CVE-2025-39844 Référence CVE CVE-2025-39845 https://www.cve.org/CVERecord?id=CVE-2025-39845 Référence CVE CVE-2025-39846 https://www.cve.org/CVERecord?id=CVE-2025-39846 Référence CVE CVE-2025-39847 https://www.cve.org/CVERecord?id=CVE-2025-39847 Référence CVE CVE-2025-39848 https://www.cve.org/CVERecord?id=CVE-2025-39848 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 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-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 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-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-39920 https://www.cve.org/CVERecord?id=CVE-2025-39920 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40018 https://www.cve.org/CVERecord?id=CVE-2025-40018 Référence CVE CVE-2025-40025 https://www.cve.org/CVERecord?id=CVE-2025-40025 Référence CVE CVE-2025-40026 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39756 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=CVE-2025-39841 Référence CVE CVE-2025-39851 https://www.cve.org/CVERecord?id=CVE-2025-39851 Référence CVE CVE-2025-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CVE-2025-39876 Référence CVE CVE-2025-39881 https://www.cve.org/CVERecord?id=CVE-2025-39881 Référence CVE CVE-2025-39895 https://www.cve.org/CVERecord?id=CVE-2025-39895 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-39911 https://www.cve.org/CVERecord?id=CVE-2025-39911 Référence CVE CVE-2025-39923 https://www.cve.org/CVERecord?id=CVE-2025-39923 Référence CVE CVE-2025-39929 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39849 Référence CVE CVE-2025-39850 https://www.cve.org/CVERecord?id=CVE-2025-39850 Référence CVE CVE-2025-39851 https://www.cve.org/CVERecord?id=CVE-2025-39851 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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-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-39889 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39849 Référence CVE CVE-2025-39850 https://www.cve.org/CVERecord?id=CVE-2025-39850 Référence CVE CVE-2025-39851 https://www.cve.org/CVERecord?id=CVE-2025-39851 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-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-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-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-39889 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-39846 Référence CVE CVE-2025-39847 https://www.cve.org/CVERecord?id=CVE-2025-39847 Référence CVE CVE-2025-39848 https://www.cve.org/CVERecord?id=CVE-2025-39848 Référence CVE CVE-2025-39849 https://www.cve.org/CVERecord?id=CVE-2025-39849 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 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-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-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=

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

d?id=CVE-2025-39852 Référence CVE CVE-2025-39853 https://www.cve.org/CVERecord?id=CVE-2025-39853 Référence CVE CVE-2025-39854 https://www.cve.org/CVERecord?id=CVE-2025-39854 Référence CVE CVE-2025-39857 https://www.cve.org/CVERecord?id=CVE-2025-39857 Référence CVE CVE-2025-39860 https://www.cve.org/CVERecord?id=CVE-2025-39860 Référence CVE CVE-2025-39861 https://www.cve.org/CVERecord?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-39866 https://www.cve.org/CVERecord?id=CVE-2025-39866 Référence CVE CVE-2025-40300 https://www.cve.org/CVERecord?id=CVE-2025-40300 Gestion détaillée du document le 26 septembre 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-025307Debian等の複数ベンダの製品における解放済みメモリの使用に関する脆弱性

Linuxカーネルにおける脆弱性が修正されました。__mark_inode_dirty()関数でのuse-after-freeの問題は、inodeのスピンロックを適切に保持することで解決されました。これにより、書き込みバックの競合状態が防止され、システムの安定性とセキュリティが向上しました。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple Linux kernel updates from SUSE address critical security vulnerabilities including use-after-free, race conditions, privilege escalation, denial of service, information leaks, and the VMSCAPE branch predictor isolation flaw across various architectures and subsystems.

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: < 4.2, 5.10.247 ≤ 5.10.*, 5.15.192 ≤ 5.15.*, 6.1.151 ≤ 6.1.*, 6.6.105 ≤ 6.6.*, 6.12.46 ≤ 6.12.*, 6.16.6 ≤ 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 19 Sept 2025 · Last source change 8 Sept 2026, 08:42 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-30334
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    0747259d13febfcc838980a63c414c9b920cea6f < e2a14bbae5d8bacaa301362744a110e2be40a3a3; 0747259d13febfcc838980a63c414c9b920cea6f < b187c976111960e6e54a6b1fff724f6e3d39406c; 0747259d13febfcc838980a63c414c9b920cea6f < 1edc2feb9c759a9883dfe81cb5ed231412d8b2e4; 0747259d13febfcc838980a63c414c9b920cea6f < bf89b1f87c72df79cf76203f71fbf8349cd5c9de; 0747259d13febfcc838980a63c414c9b920cea6f < e63052921f1b25a836feb1500b841bff7a4a0456; 0747259d13febfcc838980a63c414c9b920cea6f < c8c14adf80bd1a6e4a1d7ee9c2a816881c26d17a; 0747259d13febfcc838980a63c414c9b920cea6f < d02d2c98d25793902f65803ab853b592c7a96b29; 4.2 · Fixed: < 4.2; 5.10.247 ≤ 5.10.*; 5.15.192 ≤ 5.15.*; 6.1.151 ≤ 6.1.*; 6.6.105 ≤ 6.6.*; 6.12.46 ≤ 6.12.*; 6.16.6 ≤ 6.16.*; 6.17 ≤ *
    After
    Linux: 0747259d13febfcc838980a63c414c9b920cea6f < e2a14bbae5d8bacaa301362744a110e2be40a3a3, 0747259d13febfcc838980a63c414c9b920cea6f < b187c976111960e6e54a6b1fff724f6e3d39406c, 0747259d13febfcc838980a63c414c9b920cea6f < 1edc2feb9c759a9883dfe81cb5ed231412d8b2e4, 0747259d13febfcc838980a63c414c9b920cea6f < bf89b1f87c72df79cf76203f71fbf8349cd5c9de, 0747259d13febfcc838980a63c414c9b920cea6f < e63052921f1b25a836feb1500b841bff7a4a0456, 0747259d13febfcc838980a63c414c9b920cea6f < c8c14adf80bd1a6e4a1d7ee9c2a816881c26d17a, 0747259d13febfcc838980a63c414c9b920cea6f < d02d2c98d25793902f65803ab853b592c7a96b29, 4.2 · Fixed: Linux: < 4.2, 5.10.247 ≤ 5.10.*, 5.15.192 ≤ 5.15.*, 6.1.151 ≤ 6.1.*, 6.6.105 ≤ 6.6.*, 6.12.46 ≤ 6.12.*, 6.16.6 ≤ 6.16.*, 6.17 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-30334↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-39866 · cve.blacktree.nl