BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2025-38677High confidence

f2fs: fix to avoid out-of-boundary access in dnode page

Linux · Linux

7.8HighCVSS 3.1

Recommended action

Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

21 package states

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.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-intel`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, 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 feed`	Canonical record ↗Source updated 8 Sept 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

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: f2fs: fix to avoid out-of-boundary access in dnode page As Jiaming Zhang reported: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x1c1/0x2a0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x17e/0x800 mm/kasan/report.c:480 kasan_report+0x147/0x180 mm/kasan/report.c:593 data_blkaddr fs/f2fs/f2fs.h:3053 [inline] f2fs_data_blkaddr fs/f2fs/f2fs.h:3058 [inline] f2fs_get_dnode_of_data+0x1a09/0x1c40 fs/f2fs/node.c:855 f2fs_reserve_block+0x53/0x310 fs/f2fs/data.c:1195 prepare_write_begin fs/f2fs/data.c:3395 [inline] f2fs_write_begin+0xf39/0x2190 fs/f2fs/data.c:3594 generic_perform_write+0x2c7/0x910 mm/filemap.c:4112 f2fs_buffered_write_iter fs/f2fs/file.c:4988 [inline] f2fs_file_write_iter+0x1ec8/0x2410 fs/f2fs/file.c:5216 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x546/0xa90 fs/read_write.c:686 ksys_write+0x149/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x3d0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in the corrupted image, there is a dnode has the same node id w/ its inode, so during f2fs_get_dnode_of_data(), it tries to access block address in dnode at offset 934, however it parses the dnode as inode node, so that get_dnode_addr() returns 360, then it tries to access page address from 360 + 934 * 4 = 4096 w/ 4 bytes. To fix this issue, let's add sanity check for node id of all direct nodes during f2fs_get_dnode_of_data().
Remediation: Update to V5.0 or later version

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-27938

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid out-of-boundary access in dnode page As Jiaming Zhang reported: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x1c1/0x2a0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x17e/0x800 mm/kasan/report.c:480 kasan_report+0x147/0x180 mm/kasan/report.c:593 data_blkaddr fs/f2fs/f2fs.h:3053 [inline] f2fs_data_blkaddr fs/f2fs/f2fs.h:3058 [inline] f2fs_get_dnode_of_data+0x1a09/0x1c40 fs/f2fs/node.c:855 f2fs_reserve_block+0x53/0x310 fs/f2fs/data.c:1195 prepare_write_begin fs/f2fs/data.c:3395 [inline] f2fs_write_begin+0xf39/0x2190 fs/f2fs/data.c:3594 generic_perform_write+0x2c7/0x910 mm/filemap.c:4112 f2fs_buffered_write_iter fs/f2fs/file.c:4988 [inline] f2fs_file_write_iter+0x1ec8/0x2410 fs/f2fs/file.c:5216 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x546/0xa90 fs/read_write.c:686 ksys_write+0x149/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf3/0x3d0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is in the corrupted image, there is a dnode has the same node id w/ its inode, so during f2fs_get_dnode_of_data(), it tries to access block address in dnode at offset 934, however it parses the dnode as inode node, so that get_dnode_addr() returns 360, then it tries to access page address from 360 + 934 * 4 = 4096 w/ 4 bytes. To fix this issue, let's add sanity check for node id of all direct nodes during f2fs_get_dnode_of_data().

What

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

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 → Out-of-bounds Read → 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-125 ↗
CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.
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-125

Official authority intelligence

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

ENISA EUVD · EUVD-2025-27938Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2025-1933Linux Kernel: Eine Schwachstelle ermöglicht einen Denial of Service

Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory

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

d?id=CVE-2025-37968 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38347 https://www.cve.org/CVERecord?id=CVE-2025-38347 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38552 https://www.cve.org/CVERecord?id=CVE-2025-38552 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38687 https://www.cve.org/CVERecord?id=CVE-2025-38687 Référence CVE CVE-2025-38691 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2025-38660 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38686 https://www.cve.org/CVERecord?id=CVE-2025-38686 Référence CVE CVE-2025-38687 https://www.cve.org/CVERecord?id=CVE-2025-38687 Référence CVE CVE-2025-38688 https://www.cve.org/CVERecord?id=

Official advisory

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

d?id=CVE-2025-38660 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38686 https://www.cve.org/CVERecord?id=CVE-2025-38686 Référence CVE CVE-2025-38687 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-38660 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38686 https://www.cve.org/CVERecord?id=CVE-2025-38686 Référence CVE CVE-2025-38687 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-38660 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38686 https://www.cve.org/CVERecord?id=CVE-2025-38686 Référence CVE CVE-2025-38687 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-38660 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38686 https://www.cve.org/CVERecord?id=CVE-2025-38686 Référence CVE CVE-2025-38687 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-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38666 https://www.cve.org/CVERecord?id=CVE-2025-38666 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38675 https://www.cve.org/CVERecord?id=CVE-2025-38675 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38678 https://www.cve.org/CVERecord?id=CVE-2025-38678 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38687 https://www.cve.org/CVERecord?id=CVE-2025-38687 Référence CVE CVE-2025-38691 https://www.cve.org/CVERecord?id=

Official advisory

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

Official advisory

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

d?id=CVE-2025-38653 Référence CVE CVE-2025-38663 https://www.cve.org/CVERecord?id=CVE-2025-38663 Référence CVE CVE-2025-38664 https://www.cve.org/CVERecord?id=CVE-2025-38664 Référence CVE CVE-2025-38665 https://www.cve.org/CVERecord?id=CVE-2025-38665 Référence CVE CVE-2025-38666 https://www.cve.org/CVERecord?id=CVE-2025-38666 Référence CVE CVE-2025-38668 https://www.cve.org/CVERecord?id=CVE-2025-38668 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38671 https://www.cve.org/CVERecord?id=CVE-2025-38671 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38687 https://www.cve.org/CVERecord?id=CVE-2025-38687 Référence CVE CVE-2025-38691 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-38347 Référence CVE CVE-2025-38453 https://www.cve.org/CVERecord?id=CVE-2025-38453 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=CVE-2025-38502 Référence CVE CVE-2025-38552 https://www.cve.org/CVERecord?id=CVE-2025-38552 Référence CVE CVE-2025-38556 https://www.cve.org/CVERecord?id=CVE-2025-38556 Référence CVE CVE-2025-38614 https://www.cve.org/CVERecord?id=CVE-2025-38614 Référence CVE CVE-2025-38670 https://www.cve.org/CVERecord?id=CVE-2025-38670 Référence CVE CVE-2025-38676 https://www.cve.org/CVERecord?id=CVE-2025-38676 Référence CVE CVE-2025-38677 https://www.cve.org/CVERecord?id=CVE-2025-38677 Référence CVE CVE-2025-38679 https://www.cve.org/CVERecord?id=CVE-2025-38679 Référence CVE CVE-2025-38680 https://www.cve.org/CVERecord?id=CVE-2025-38680 Référence CVE CVE-2025-38681 https://www.cve.org/CVERecord?id=CVE-2025-38681 Référence CVE CVE-2025-38683 https://www.cve.org/CVERecord?id=CVE-2025-38683 Référence CVE CVE-2025-38684 https://www.cve.org/CVERecord?id=CVE-2025-38684 Référence CVE CVE-2025-38685 https://www.cve.org/CVERecord?id=CVE-2025-38685 Référence CVE CVE-2025-38687 https://www.cve.org/CVERecord?id=CVE-2025-38687 Référence CVE CVE-2025-38691 https://www.cve.org/CVERecord?id=

Official advisory

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

A comprehensive Linux kernel update fixed multiple security vulnerabilities including out-of-boundary access in the f2fs filesystem, CPU cache initialization flaws, AMD processor data leakage, and the VMSCAPE branch predictor isolation issue across various architectures and subsystems.

Official advisory

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.: Patch available
Affected: SIMATIC CN 4100
Fixed: < 3.8; 5.4.297 ≤ 5.4.*; 5.10.241 ≤ 5.10.*; 5.15.190 ≤ 5.15.*; 6.1.149 ≤ 6.1.*; 6.6.103 ≤ 6.6.*; 6.12.44 ≤ 6.12.*; 6.16.4 ≤ 6.16.*
Action: Update to V5.0 or later version
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 30 Aug 2025 · Last source change 5 Aug 2026, 12:03 UTC · CWE-125 · Out-of-bounds Read

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-27938

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

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 →

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

2025-08-30CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2025-27938↗Vendor CSAF · Siemens ProductCERT↗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.

f2fs: fix to avoid out-of-boundary access in dnode page

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

EUVD-2025-27938

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

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