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

mptcp: make fallback action and fallback decision atomic

Linux · Linux

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 22 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.21% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 30 daysRemediation target: Within 180 days

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-38491 · CSAF 2.0 · revision 60 · interimSUSE Product Security TeamCVE-2025-38491
81 known affected

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

  • 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 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---
Remediation
Update to V5.0 or later version
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2025-22872

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 22 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: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: <IRQ> tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 </IRQ> <TASK> __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: <IRQ> tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 </IRQ> <TASK> __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: mptcp: make fallback action and fallback decision atomic Syzkaller reported the following splat: WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline] WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Modules linked in: CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary) Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline] RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline] RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline] RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153 Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 <0f> 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00 RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45 RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001 RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000 FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0 Call Trace: <IRQ> tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432 tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975 tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166 tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925 tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363 ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233 NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254 dst_input include/net/dst.h:469 [inline] ip_rcv_finish net/ipv4/ip_input.c:447 [inline] NF_HOOK include/linux/netfilter.h:317 [inline] NF_HOOK include/linux/netfilter.h:311 [inline] ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567 __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975 __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088 process_backlog+0x301/0x1360 net/core/dev.c:6440 __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453 napi_poll net/core/dev.c:7517 [inline] net_rx_action+0xb44/0x1010 net/core/dev.c:7644 handle_softirqs+0x1d0/0x770 kernel/softirq.c:579 do_softirq+0x3f/0x90 kernel/softirq.c:480 </IRQ> <TASK> __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407 local_bh_enable include/linux/bottom_half.h:33 [inline] inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524 mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985 mptcp_check_listen_stop net/mptcp/mib.h:118 [inline] __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000 mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066 inet_release+0xed/0x200 net/ipv4/af_inet.c:435 inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x402/0xb70 fs/file_table.c:465 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xd4 ---truncated---

Why

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

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

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

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.ILowIntegrity impact: A successful attack can cause a limited loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-667
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1665Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250730Security Bulletin 30 Jul 2025 [827KB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Jul 2025 [827KB], published on 30 July 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-58240 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-31257 https://www.cve.org/CVERecord?id=CVE-2025-31257 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37968 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2025-38425 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=CVE-2025-38436 Référence CVE CVE-2025-38437 https://www.cve.org/CVERecord?id=CVE-2025-38437 Référence CVE CVE-2025-38438 https://www.cve.org/CVERecord?id=CVE-2025-38438 Référence CVE CVE-2025-38440 https://www.cve.org/CVERecord?id=CVE-2025-38440 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=CVE-2025-38449 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38486 https://www.cve.org/CVERecord?id=CVE-2025-38486 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38544 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38425 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=CVE-2025-38436 Référence CVE CVE-2025-38437 https://www.cve.org/CVERecord?id=CVE-2025-38437 Référence CVE CVE-2025-38438 https://www.cve.org/CVERecord?id=CVE-2025-38438 Référence CVE CVE-2025-38440 https://www.cve.org/CVERecord?id=CVE-2025-38440 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=CVE-2025-38449 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38486 https://www.cve.org/CVERecord?id=CVE-2025-38486 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38507 https://www.cve.org/CVERecord?id=CVE-2025-38507 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38520 https://www.cve.org/CVERecord?id=CVE-2025-38520 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38544 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-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 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-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 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-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 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-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 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-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 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-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38484 https://www.cve.org/CVERecord?id=CVE-2025-38484 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38492 https://www.cve.org/CVERecord?id=CVE-2025-38492 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 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-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38484 https://www.cve.org/CVERecord?id=CVE-2025-38484 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38484 https://www.cve.org/CVERecord?id=CVE-2025-38484 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38492 https://www.cve.org/CVERecord?id=CVE-2025-38492 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38484 https://www.cve.org/CVERecord?id=CVE-2025-38484 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38492 https://www.cve.org/CVERecord?id=CVE-2025-38492 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38456 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=CVE-2025-38513 Référence CVE CVE-2025-38514 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-38477 Référence CVE CVE-2025-38478 https://www.cve.org/CVERecord?id=CVE-2025-38478 Référence CVE CVE-2025-38480 https://www.cve.org/CVERecord?id=CVE-2025-38480 Référence CVE CVE-2025-38481 https://www.cve.org/CVERecord?id=CVE-2025-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38501 https://www.cve.org/CVERecord?id=CVE-2025-38501 Référence CVE CVE-2025-38502 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38511 https://www.cve.org/CVERecord?id=CVE-2025-38511 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 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-23143 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37968 https://www.cve.org/CVERecord?id=CVE-2025-37968 Référence CVE CVE-2025-38272 https://www.cve.org/CVERecord?id=CVE-2025-38272 Référence CVE CVE-2025-38306 https://www.cve.org/CVERecord?id=CVE-2025-38306 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-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=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 https://www.cve.org/CVERecord?id=CVE-2025-38512 Référence CVE CVE-2025-38513 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38439 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=CVE-2025-38503 Référence CVE CVE-2025-38506 https://www.cve.org/CVERecord?id=CVE-2025-38506 Référence CVE CVE-2025-38510 https://www.cve.org/CVERecord?id=CVE-2025-38510 Référence CVE CVE-2025-38512 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-38481 Référence CVE CVE-2025-38482 https://www.cve.org/CVERecord?id=CVE-2025-38482 Référence CVE CVE-2025-38483 https://www.cve.org/CVERecord?id=CVE-2025-38483 Référence CVE CVE-2025-38484 https://www.cve.org/CVERecord?id=CVE-2025-38484 Référence CVE CVE-2025-38485 https://www.cve.org/CVERecord?id=CVE-2025-38485 Référence CVE CVE-2025-38487 https://www.cve.org/CVERecord?id=CVE-2025-38487 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38489 https://www.cve.org/CVERecord?id=CVE-2025-38489 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38493 https://www.cve.org/CVERecord?id=CVE-2025-38493 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38496 https://www.cve.org/CVERecord?id=CVE-2025-38496 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=

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

LinuxカーネルのMPTCP(マルチパスTCP)において、フォールバック処理のアトミック性が欠如していることによる警告がsyzkallerにより報告されました。この問題は、mptcpのフォールバック判定とアクションを同時に実行できるよう修正され、警告の発生を回避し、安全性が向上しました。

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

Multiple security vulnerabilities in the Linux kernel, including atomicity issues in the mptcp subsystem, CPU cache initialization flaws, and AMD processor data leaks, were fixed across various SUSE Linux Enterprise and Micro kernel versions affecting numerous subsystems and architectures.

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: < 5.19, 6.1.149 ≤ 6.1.*, 6.6.101 ≤ 6.6.*, 6.12.40 ≤ 6.12.*, 6.15.8 ≤ 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 28 Jul 2025 · Last source change 5 Aug 2026, 12:02 UTC · CWE-667 · Improper Locking

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-22872
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
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-38491 · cve.blacktree.nl