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

ext4: inline: fix len overflow in ext4_prepare_inline_data

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 26 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.35-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.147-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.35-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.35-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-38222 · CSAF 2.0 · revision 56 · interimSUSE Product Security TeamCVE-2025-38222
408 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
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below. fd = open("file1", O_RDWR | O_CREAT | O_TRUNC, 0666); ftruncate(fd, 30); pwrite(fd, "a", 1, (1UL EXT4_I(inode)->i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [ 44.545164] ------------[ cut here ]------------ [ 44.545530] kernel BUG at fs/ext4/inline.c:240! [ 44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [ 44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [ 44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b 0b 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 20 49 [ 44.546523] RSP: 0018:ffffb342008b79a8 EFLAGS: 00010216 [ 44.546523] RAX: 0000000000000001 RBX: ffff9329c579c000 RCX: 0000010000000006 [ 44.546523] RDX: 000000000000003c RSI: ffffb342008b79f0 RDI: ffff9329c158e738 [ 44.546523] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 [ 44.546523] R10: 00007ffffffff000 R11: ffffffff9bd0d910 R12: 0000006210000000 [ 44.546523] R13: fffffc7e4015e700 R14: 0000010000000005 R15: ffff9329c158e738 [ 44.546523] FS: 00007f4299934740(0000) GS:ffff932a60179000(0000) knlGS:0000000000000000 [ 44.546523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 44.546523] CR2: 00007f4299a1ec90 CR3: 0000000002886002 CR4: 0000000000770eb0 [ 44.546523] PKRU: 55555554 [ 44.546523] Call Trace: [ 44.546523] [ 44.546523] ext4_write_inline_data_end+0x126/0x2d0 [ 44.546523] generic_perform_write+0x17e/0x270 [ 44.546523] ext4_buffered_write_iter+0xc8/0x170 [ 44.546523] vfs_write+0x2be/0x3e0 [ 44.546523] __x64_sys_pwrite64+0x6d/0xc0 [ 44.546523] do_syscall_64+0x6a/0xf0 [ 44.546523] ? __wake_up+0x89/0xb0 [ 44.546523] ? xas_find+0x72/0x1c0 [ 44.546523] ? next_uptodate_folio+0x317/0x330 [ 44.546523] ? set_pte_range+0x1a6/0x270 [ 44.546523] ? filemap_map_pages+0x6ee/0x840 [ 44.546523] ? ext4_setattr+0x2fa/0x750 [ 44.546523] ? do_pte_missing+0x128/0xf70 [ 44.546523] ? security_inode_post_setattr+0x3e/0xd0 [ 44.546523] ? ___pte_offset_map+0x19/0x100 [ 44.546523] ? handle_mm_fault+0x721/0xa10 [ 44.546523] ? do_user_addr_fault+0x197/0x730 [ 44.546523] ? do_syscall_64+0x76/0xf0 [ 44.546523] ? arch_exit_to_user_mode_prepare+0x1e/0x60 [ 44.546523] ? irqentry_exit_to_user_mode+0x79/0x90 [ 44.546523] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 44.546523] RIP: 0033:0x7f42999c6687 [ 44.546523] Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff [ 44.546523] RSP: 002b:00007ffeae4a7930 EFLAGS: 00000202 ORIG_RAX: 0000000000000012 [ 44.546523] RAX: ffffffffffffffda RBX: 00007f4299934740 RCX: 00007f42999c6687 [ 44.546523] RDX: 0000000000000001 RSI: 000055ea6149200f RDI: 0000000000000003 [ 44.546523] RBP: 00007ffeae4a79a0 R08: 0000000000000000 R09: 0000000000000000 [ 44.546523] R10: 0000010000000005 R11: 0000000000000202 R12: 0000 ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below. fd = open("file1", O_RDWR | O_CREAT | O_TRUNC, 0666); ftruncate(fd, 30); pwrite(fd, "a", 1, (1UL EXT4_I(inode)->i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [ 44.545164] ------------[ cut here ]------------ [ 44.545530] kernel BUG at fs/ext4/inline.c:240! [ 44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [ 44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [ 44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b 0b 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 20 49 [ 44.546523] RSP: 0018:ffffb342008b79a8 EFLAGS: 00010216 [ 44.546523] RAX: 0000000000000001 RBX: ffff9329c579c000 RCX: 0000010000000006 [ 44.546523] RDX: 000000000000003c RSI: ffffb342008b79f0 RDI: ffff9329c158e738 [ 44.546523] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 [ 44.546523] R10: 00007ffffffff000 R11: ffffffff9bd0d910 R12: 0000006210000000 [ 44.546523] R13: fffffc7e4015e700 R14: 0000010000000005 R15: ffff9329c158e738 [ 44.546523] FS: 00007f4299934740(0000) GS:ffff932a60179000(0000) knlGS:0000000000000000 [ 44.546523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 44.546523] CR2: 00007f4299a1ec90 CR3: 0000000002886002 CR4: 0000000000770eb0 [ 44.546523] PKRU: 55555554 [ 44.546523] Call Trace: [ 44.546523] [ 44.546523] ext4_write_inline_data_end+0x126/0x2d0 [ 44.546523] generic_perform_write+0x17e/0x270 [ 44.546523] ext4_buffered_write_iter+0xc8/0x170 [ 44.546523] vfs_write+0x2be/0x3e0 [ 44.546523] __x64_sys_pwrite64+0x6d/0xc0 [ 44.546523] do_syscall_64+0x6a/0xf0 [ 44.546523] ? __wake_up+0x89/0xb0 [ 44.546523] ? xas_find+0x72/0x1c0 [ 44.546523] ? next_uptodate_folio+0x317/0x330 [ 44.546523] ? set_pte_range+0x1a6/0x270 [ 44.546523] ? filemap_map_pages+0x6ee/0x840 [ 44.546523] ? ext4_setattr+0x2fa/0x750 [ 44.546523] ? do_pte_missing+0x128/0xf70 [ 44.546523] ? security_inode_post_setattr+0x3e/0xd0 [ 44.546523] ? ___pte_offset_map+0x19/0x100 [ 44.546523] ? handle_mm_fault+0x721/0xa10 [ 44.546523] ? do_user_addr_fault+0x197/0x730 [ 44.546523] ? do_syscall_64+0x76/0xf0 [ 44.546523] ? arch_exit_to_user_mode_prepare+0x1e/0x60 [ 44.546523] ? irqentry_exit_to_user_mode+0x79/0x90 [ 44.546523] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 44.546523] RIP: 0033:0x7f42999c6687 [ 44.546523] Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff [ 44.546523] RSP: 002b:00007ffeae4a7930 EFLAGS: 00000202 ORIG_RAX: 0000000000000012 [ 44.546523] RAX: ffffffffffffffda RBX: 00007f4299934740 RCX: 00007f42999c6687 [ 44.546523] RDX: 0000000000000001 RSI: 000055ea6149200f RDI: 0000000000000003 [ 44.546523] RBP: 00007ffeae4a79a0 R08: 0000000000000000 R09: 0000000000000000 [ 44.546523] R10: 0000010000000005 R11: 0000000000000202 R12: 0000 ---truncated---
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-20034

No EUVD known-exploited evidence

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

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 26 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: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below. fd = open("file1", O_RDWR | O_CREAT | O_TRUNC, 0666); ftruncate(fd, 30); pwrite(fd, "a", 1, (1UL << 40) + 5UL); That happens because write_begin will succeed as when ext4_generic_write_inline_data calls ext4_prepare_inline_data, pos + len will be truncated, leading to ext4_prepare_inline_data parameter to be 6 instead of 0x10000000006. Then, later when write_end is called, we hit: BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [ 44.545164] ------------[ cut here ]------------ [ 44.545530] kernel BUG at fs/ext4/inline.c:240! [ 44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [ 44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [ 44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b <0f> 0b 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 20 49 [ 44.546523] RSP: 0018:ffffb342008b79a8 EFLAGS: 00010216 [ 44.546523] RAX: 0000000000000001 RBX: ffff9329c579c000 RCX: 0000010000000006 [ 44.546523] RDX: 000000000000003c RSI: ffffb342008b79f0 RDI: ffff9329c158e738 [ 44.546523] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 [ 44.546523] R10: 00007ffffffff000 R11: ffffffff9bd0d910 R12: 0000006210000000 [ 44.546523] R13: fffffc7e4015e700 R14: 0000010000000005 R15: ffff9329c158e738 [ 44.546523] FS: 00007f4299934740(0000) GS:ffff932a60179000(0000) knlGS:0000000000000000 [ 44.546523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 44.546523] CR2: 00007f4299a1ec90 CR3: 0000000002886002 CR4: 0000000000770eb0 [ 44.546523] PKRU: 55555554 [ 44.546523] Call Trace: [ 44.546523] <TASK> [ 44.546523] ext4_write_inline_data_end+0x126/0x2d0 [ 44.546523] generic_perform_write+0x17e/0x270 [ 44.546523] ext4_buffered_write_iter+0xc8/0x170 [ 44.546523] vfs_write+0x2be/0x3e0 [ 44.546523] __x64_sys_pwrite64+0x6d/0xc0 [ 44.546523] do_syscall_64+0x6a/0xf0 [ 44.546523] ? __wake_up+0x89/0xb0 [ 44.546523] ? xas_find+0x72/0x1c0 [ 44.546523] ? next_uptodate_folio+0x317/0x330 [ 44.546523] ? set_pte_range+0x1a6/0x270 [ 44.546523] ? filemap_map_pages+0x6ee/0x840 [ 44.546523] ? ext4_setattr+0x2fa/0x750 [ 44.546523] ? do_pte_missing+0x128/0xf70 [ 44.546523] ? security_inode_post_setattr+0x3e/0xd0 [ 44.546523] ? ___pte_offset_map+0x19/0x100 [ 44.546523] ? handle_mm_fault+0x721/0xa10 [ 44.546523] ? do_user_addr_fault+0x197/0x730 [ 44.546523] ? do_syscall_64+0x76/0xf0 [ 44.546523] ? arch_exit_to_user_mode_prepare+0x1e/0x60 [ 44.546523] ? irqentry_exit_to_user_mode+0x79/0x90 [ 44.546523] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 44.546523] RIP: 0033:0x7f42999c6687 [ 44.546523] Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff [ 44.546523] RSP: 002b:00007ffeae4a7930 EFLAGS: 00000202 ORIG_RAX: 0000000000000012 [ 44.546523] RAX: ffffffffffffffda RBX: 00007f4299934740 RCX: 00007f42999c6687 [ 44.546523] RDX: 0000000000000001 RSI: 000055ea6149200f RDI: 0000000000000003 [ 44.546523] RBP: 00007ffeae4a79a0 R08: 0000000000000000 R09: 0000000000000000 [ 44.546523] R10: 0000010000000005 R11: 0000000000000202 R12: 0000 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below. fd = open("file1", O_RDWR | O_CREAT | O_TRUNC, 0666); ftruncate(fd, 30); pwrite(fd, "a", 1, (1UL << 40) + 5UL); That happens because write_begin will succeed as when ext4_generic_write_inline_data calls ext4_prepare_inline_data, pos + len will be truncated, leading to ext4_prepare_inline_data parameter to be 6 instead of 0x10000000006. Then, later when write_end is called, we hit: BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [ 44.545164] ------------[ cut here ]------------ [ 44.545530] kernel BUG at fs/ext4/inline.c:240! [ 44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [ 44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [ 44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b <0f> 0b 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 20 49 [ 44.546523] RSP: 0018:ffffb342008b79a8 EFLAGS: 00010216 [ 44.546523] RAX: 0000000000000001 RBX: ffff9329c579c000 RCX: 0000010000000006 [ 44.546523] RDX: 000000000000003c RSI: ffffb342008b79f0 RDI: ffff9329c158e738 [ 44.546523] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 [ 44.546523] R10: 00007ffffffff000 R11: ffffffff9bd0d910 R12: 0000006210000000 [ 44.546523] R13: fffffc7e4015e700 R14: 0000010000000005 R15: ffff9329c158e738 [ 44.546523] FS: 00007f4299934740(0000) GS:ffff932a60179000(0000) knlGS:0000000000000000 [ 44.546523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 44.546523] CR2: 00007f4299a1ec90 CR3: 0000000002886002 CR4: 0000000000770eb0 [ 44.546523] PKRU: 55555554 [ 44.546523] Call Trace: [ 44.546523] <TASK> [ 44.546523] ext4_write_inline_data_end+0x126/0x2d0 [ 44.546523] generic_perform_write+0x17e/0x270 [ 44.546523] ext4_buffered_write_iter+0xc8/0x170 [ 44.546523] vfs_write+0x2be/0x3e0 [ 44.546523] __x64_sys_pwrite64+0x6d/0xc0 [ 44.546523] do_syscall_64+0x6a/0xf0 [ 44.546523] ? __wake_up+0x89/0xb0 [ 44.546523] ? xas_find+0x72/0x1c0 [ 44.546523] ? next_uptodate_folio+0x317/0x330 [ 44.546523] ? set_pte_range+0x1a6/0x270 [ 44.546523] ? filemap_map_pages+0x6ee/0x840 [ 44.546523] ? ext4_setattr+0x2fa/0x750 [ 44.546523] ? do_pte_missing+0x128/0xf70 [ 44.546523] ? security_inode_post_setattr+0x3e/0xd0 [ 44.546523] ? ___pte_offset_map+0x19/0x100 [ 44.546523] ? handle_mm_fault+0x721/0xa10 [ 44.546523] ? do_user_addr_fault+0x197/0x730 [ 44.546523] ? do_syscall_64+0x76/0xf0 [ 44.546523] ? arch_exit_to_user_mode_prepare+0x1e/0x60 [ 44.546523] ? irqentry_exit_to_user_mode+0x79/0x90 [ 44.546523] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 44.546523] RIP: 0033:0x7f42999c6687 [ 44.546523] Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff [ 44.546523] RSP: 002b:00007ffeae4a7930 EFLAGS: 00000202 ORIG_RAX: 0000000000000012 [ 44.546523] RAX: ffffffffffffffda RBX: 00007f4299934740 RCX: 00007f42999c6687 [ 44.546523] RDX: 0000000000000001 RSI: 000055ea6149200f RDI: 0000000000000003 [ 44.546523] RBP: 00007ffeae4a79a0 R08: 0000000000000000 R09: 0000000000000000 [ 44.546523] R10: 0000010000000005 R11: 0000000000000202 R12: 0000 ---truncated---

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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: ext4: inline: fix len overflow in ext4_prepare_inline_data When running the following code on an ext4 filesystem with inline_data feature enabled, it will lead to the bug below. fd = open("file1", O_RDWR | O_CREAT | O_TRUNC, 0666); ftruncate(fd, 30); pwrite(fd, "a", 1, (1UL << 40) + 5UL); That happens because write_begin will succeed as when ext4_generic_write_inline_data calls ext4_prepare_inline_data, pos + len will be truncated, leading to ext4_prepare_inline_data parameter to be 6 instead of 0x10000000006. Then, later when write_end is called, we hit: BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); at ext4_write_inline_data. Fix it by using a loff_t type for the len parameter in ext4_prepare_inline_data instead of an unsigned int. [ 44.545164] ------------[ cut here ]------------ [ 44.545530] kernel BUG at fs/ext4/inline.c:240! [ 44.545834] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 44.546172] CPU: 3 UID: 0 PID: 343 Comm: test Not tainted 6.15.0-rc2-00003-g9080916f4863 #45 PREEMPT(full) 112853fcebfdb93254270a7959841d2c6aa2c8bb [ 44.546523] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 44.546523] RIP: 0010:ext4_write_inline_data+0xfe/0x100 [ 44.546523] Code: 3c 0e 48 83 c7 48 48 89 de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e4 fa 43 01 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 0b <0f> 0b 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 20 49 [ 44.546523] RSP: 0018:ffffb342008b79a8 EFLAGS: 00010216 [ 44.546523] RAX: 0000000000000001 RBX: ffff9329c579c000 RCX: 0000010000000006 [ 44.546523] RDX: 000000000000003c RSI: ffffb342008b79f0 RDI: ffff9329c158e738 [ 44.546523] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000 [ 44.546523] R10: 00007ffffffff000 R11: ffffffff9bd0d910 R12: 0000006210000000 [ 44.546523] R13: fffffc7e4015e700 R14: 0000010000000005 R15: ffff9329c158e738 [ 44.546523] FS: 00007f4299934740(0000) GS:ffff932a60179000(0000) knlGS:0000000000000000 [ 44.546523] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 44.546523] CR2: 00007f4299a1ec90 CR3: 0000000002886002 CR4: 0000000000770eb0 [ 44.546523] PKRU: 55555554 [ 44.546523] Call Trace: [ 44.546523] <TASK> [ 44.546523] ext4_write_inline_data_end+0x126/0x2d0 [ 44.546523] generic_perform_write+0x17e/0x270 [ 44.546523] ext4_buffered_write_iter+0xc8/0x170 [ 44.546523] vfs_write+0x2be/0x3e0 [ 44.546523] __x64_sys_pwrite64+0x6d/0xc0 [ 44.546523] do_syscall_64+0x6a/0xf0 [ 44.546523] ? __wake_up+0x89/0xb0 [ 44.546523] ? xas_find+0x72/0x1c0 [ 44.546523] ? next_uptodate_folio+0x317/0x330 [ 44.546523] ? set_pte_range+0x1a6/0x270 [ 44.546523] ? filemap_map_pages+0x6ee/0x840 [ 44.546523] ? ext4_setattr+0x2fa/0x750 [ 44.546523] ? do_pte_missing+0x128/0xf70 [ 44.546523] ? security_inode_post_setattr+0x3e/0xd0 [ 44.546523] ? ___pte_offset_map+0x19/0x100 [ 44.546523] ? handle_mm_fault+0x721/0xa10 [ 44.546523] ? do_user_addr_fault+0x197/0x730 [ 44.546523] ? do_syscall_64+0x76/0xf0 [ 44.546523] ? arch_exit_to_user_mode_prepare+0x1e/0x60 [ 44.546523] ? irqentry_exit_to_user_mode+0x79/0x90 [ 44.546523] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 44.546523] RIP: 0033:0x7f42999c6687 [ 44.546523] Code: 48 89 fa 4c 89 df e8 58 b3 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff [ 44.546523] RSP: 002b:00007ffeae4a7930 EFLAGS: 00000202 ORIG_RAX: 0000000000000012 [ 44.546523] RAX: ffffffffffffffda RBX: 00007f4299934740 RCX: 00007f42999c6687 [ 44.546523] RDX: 0000000000000001 RSI: 000055ea6149200f RDI: 0000000000000003 [ 44.546523] RBP: 00007ffeae4a79a0 R08: 0000000000000000 R09: 0000000000000000 [ 44.546523] R10: 0000010000000005 R11: 0000000000000202 R12: 0000 ---truncated---

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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 → Integer Overflow or Wraparound → 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-190 ↗

CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

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

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-1465Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

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

d?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=CVE-2025-38232 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 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-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=CVE-2025-38232 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 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-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=CVE-2025-38232 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 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-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=CVE-2025-38232 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 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-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=CVE-2025-38232 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 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-38208 Référence CVE CVE-2025-38209 https://www.cve.org/CVERecord?id=CVE-2025-38209 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38213 https://www.cve.org/CVERecord?id=CVE-2025-38213 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38216 https://www.cve.org/CVERecord?id=CVE-2025-38216 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38224 https://www.cve.org/CVERecord?id=CVE-2025-38224 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38228 https://www.cve.org/CVERecord?id=CVE-2025-38228 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38232 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38200 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38245 https://www.cve.org/CVERecord?id=CVE-2025-38245 Référence CVE CVE-2025-38249 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38223 https://www.cve.org/CVERecord?id=CVE-2025-38223 Référence CVE CVE-2025-38224 https://www.cve.org/CVERecord?id=CVE-2025-38224 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38228 https://www.cve.org/CVERecord?id=CVE-2025-38228 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38197 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38245 https://www.cve.org/CVERecord?id=CVE-2025-38245 Référence CVE CVE-2025-38249 https://www.cve.org/CVERecord?id=CVE-2025-38249 Référence CVE CVE-2025-38251 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38206 Référence CVE CVE-2025-38208 https://www.cve.org/CVERecord?id=CVE-2025-38208 Référence CVE CVE-2025-38210 https://www.cve.org/CVERecord?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38223 https://www.cve.org/CVERecord?id=CVE-2025-38223 Référence CVE CVE-2025-38224 https://www.cve.org/CVERecord?id=CVE-2025-38224 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38228 https://www.cve.org/CVERecord?id=CVE-2025-38228 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38206 Référence CVE CVE-2025-38208 https://www.cve.org/CVERecord?id=CVE-2025-38208 Référence CVE CVE-2025-38210 https://www.cve.org/CVERecord?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38223 https://www.cve.org/CVERecord?id=CVE-2025-38223 Référence CVE CVE-2025-38224 https://www.cve.org/CVERecord?id=CVE-2025-38224 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38228 https://www.cve.org/CVERecord?id=CVE-2025-38228 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 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-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38197 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38244 https://www.cve.org/CVERecord?id=CVE-2025-38244 Référence CVE CVE-2025-38245 https://www.cve.org/CVERecord?id=CVE-2025-38245 Référence CVE CVE-2025-38249 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38197 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38244 https://www.cve.org/CVERecord?id=CVE-2025-38244 Référence CVE CVE-2025-38245 https://www.cve.org/CVERecord?id=CVE-2025-38245 Référence CVE CVE-2025-38249 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38197 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38204 https://www.cve.org/CVERecord?id=CVE-2025-38204 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38245 https://www.cve.org/CVERecord?id=CVE-2025-38245 Référence CVE CVE-2025-38249 https://www.cve.org/CVERecord?id=CVE-2025-38249 Référence CVE CVE-2025-38251 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38206 Référence CVE CVE-2025-38210 https://www.cve.org/CVERecord?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38213 https://www.cve.org/CVERecord?id=CVE-2025-38213 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 https://www.cve.org/CVERecord?id=CVE-2025-38239 Référence CVE CVE-2025-38244 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38206 Référence CVE CVE-2025-38210 https://www.cve.org/CVERecord?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38213 https://www.cve.org/CVERecord?id=CVE-2025-38213 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38238 https://www.cve.org/CVERecord?id=CVE-2025-38238 Référence CVE CVE-2025-38239 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38206 Référence CVE CVE-2025-38210 https://www.cve.org/CVERecord?id=CVE-2025-38210 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38213 https://www.cve.org/CVERecord?id=CVE-2025-38213 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38217 https://www.cve.org/CVERecord?id=CVE-2025-38217 Référence CVE CVE-2025-38220 https://www.cve.org/CVERecord?id=CVE-2025-38220 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38238 https://www.cve.org/CVERecord?id=CVE-2025-38238 Référence CVE CVE-2025-38239 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38198 Référence CVE CVE-2025-38200 https://www.cve.org/CVERecord?id=CVE-2025-38200 Référence CVE CVE-2025-38202 https://www.cve.org/CVERecord?id=CVE-2025-38202 Référence CVE CVE-2025-38211 https://www.cve.org/CVERecord?id=CVE-2025-38211 Référence CVE CVE-2025-38212 https://www.cve.org/CVERecord?id=CVE-2025-38212 Référence CVE CVE-2025-38214 https://www.cve.org/CVERecord?id=CVE-2025-38214 Référence CVE CVE-2025-38215 https://www.cve.org/CVERecord?id=CVE-2025-38215 Référence CVE CVE-2025-38218 https://www.cve.org/CVERecord?id=CVE-2025-38218 Référence CVE CVE-2025-38219 https://www.cve.org/CVERecord?id=CVE-2025-38219 Référence CVE CVE-2025-38222 https://www.cve.org/CVERecord?id=CVE-2025-38222 Référence CVE CVE-2025-38225 https://www.cve.org/CVERecord?id=CVE-2025-38225 Référence CVE CVE-2025-38226 https://www.cve.org/CVERecord?id=CVE-2025-38226 Référence CVE CVE-2025-38227 https://www.cve.org/CVERecord?id=CVE-2025-38227 Référence CVE CVE-2025-38229 https://www.cve.org/CVERecord?id=CVE-2025-38229 Référence CVE CVE-2025-38230 https://www.cve.org/CVERecord?id=CVE-2025-38230 Référence CVE CVE-2025-38231 https://www.cve.org/CVERecord?id=CVE-2025-38231 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38239 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-022753Linux の Linux Kernel 等複数ベンダの製品における整数オーバーフローの脆弱性

Linux の Linux Kernel 等複数ベンダの製品には、整数オーバーフローの脆弱性が存在します。

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: < 3.8, 5.4.295 ≤ 5.4.*, 5.10.239 ≤ 5.10.*, 5.15.186 ≤ 5.15.*, 6.1.142 ≤ 6.1.*, 6.6.95 ≤ 6.6.*, 6.12.35 ≤ 6.12.*, 6.15.4 ≤ 6.15.*, 6.16 ≤ *
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 4 Jul 2025 · Last source change 14 Jul 2026, 12:41 UTC · CWE-190 · Integer Overflow or Wraparound

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-20034
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-20034↗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-38222 · cve.blacktree.nl