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

smc: Fix use-after-free in __pnet_find_base_ndev().

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 2 Sep 2026

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2025-40064 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: smc: Fix use-after-free in __pnet_find_base_ndev()
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-36464

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 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: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2025-36464Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used. This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev(). While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released. We must hold dev's refcnt before calling smc_pnet_find_ism_resource(). Also, smc_pnet_find_roce_resource() has the same problem. Let's use __sk_dst_get() and dst_dev_rcu() in the two functions. [0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609 CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8 </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

Official EUVD record ↗
BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

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

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um beliebigen Code auszuführen, privilegierten Zugriff zu erlangen, sensible Informationen zu stehlen oder betroffene Systeme funktionsunfähig zu machen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251029Security Bulletin 29 Oct 2025

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

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

d?id=CVE-2025-22108 Référence CVE CVE-2025-22127 https://www.cve.org/CVERecord?id=CVE-2025-22127 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38205 https://www.cve.org/CVERecord?id=CVE-2025-38205 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38621 https://www.cve.org/CVERecord?id=CVE-2025-38621 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2026-100070 https://www.cve.org/CVERecord?id=CVE-2026-100070 Référence CVE CVE-2026-100071 https://www.cve.org/CVERecord?id=CVE-2026-100071 Référence CVE CVE-2026-100075 https://www.cve.org/CVERecord?id=CVE-2026-100075 Référence CVE CVE-2026-100078 https://www.cve.org/CVERecord?id=CVE-2026-100078 Référence CVE CVE-2026-100079 https://www.cve.org/CVER

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

d?id=CVE-2025-39859 Référence CVE CVE-2025-39862 https://www.cve.org/CVERecord?id=CVE-2025-39862 Référence CVE CVE-2025-39896 https://www.cve.org/CVERecord?id=CVE-2025-39896 Référence CVE CVE-2025-39933 https://www.cve.org/CVERecord?id=CVE-2025-39933 Référence CVE CVE-2025-39958 https://www.cve.org/CVERecord?id=CVE-2025-39958 Référence CVE CVE-2025-39990 https://www.cve.org/CVERecord?id=CVE-2025-39990 Référence CVE CVE-2025-40025 https://www.cve.org/CVERecord?id=CVE-2025-40025 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40054 https://www.cve.org/CVERecord?id=CVE-2025-40054 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-40203 https://www.cve.org/CVERecord?id=CVE-2025-40203 Référence CVE CVE-2025-40274 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38117 Référence CVE CVE-2025-38203 https://www.cve.org/CVERecord?id=CVE-2025-38203 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38237 https://www.cve.org/CVERecord?id=CVE-2025-38237 Référence CVE CVE-2025-38616 https://www.cve.org/CVERecord?id=CVE-2025-38616 Référence CVE CVE-2025-39833 https://www.cve.org/CVERecord?id=CVE-2025-39833 Référence CVE CVE-2025-39901 https://www.cve.org/CVERecord?id=CVE-2025-39901 Référence CVE CVE-2025-39925 https://www.cve.org/CVERecord?id=CVE-2025-39925 Référence CVE CVE-2025-40054 https://www.cve.org/CVERecord?id=CVE-2025-40054 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40139 https://www.cve.org/CVERecord?id=CVE-2025-40139 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40206 https://www.cve.org/CVERecord?id=CVE-2025-40206 Référence CVE CVE-2025-40307 https://www.cve.org/CVERecord?id=CVE-2025-40307 Référence CVE CVE-2025-68794 https://www.cve.org/CVERecord?id=CVE-2025-68794 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0539Multiples vulnérabilités dans Juniper Networks Secure Analytics

De multiples vulnérabilités ont été découvertes dans Juniper Networks Secure Analytics. Elles permettent à un attaquant de provoquer un déni de service à distance et un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0496Multiples vulnérabilités dans le noyau Linux de Red Hat

sécurité Red Hat RHSA-2026:9870 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9870 Référence CVE CVE-2022-50053 https://www.cve.org/CVERecord?id=CVE-2022-50053 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38180 https://www.cve.org/CVERecord?id=CVE-2025-38180 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=CVE-2025-68800 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23066 https://www.cve.org/CVERecord?id=CVE-2026-23066 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23144 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0423Multiples vulnérabilités dans le noyau Linux de Red Hat

errata/RHSA-2026:7100 Référence CVE CVE-2021-4460 https://www.cve.org/CVERecord?id=CVE-2021-4460 Référence CVE CVE-2022-49674 https://www.cve.org/CVERecord?id=CVE-2022-49674 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2025-38109 https://www.cve.org/CVERecord?id=CVE-2025-38109 Référence CVE CVE-2025-38154 https://www.cve.org/CVERecord?id=CVE-2025-38154 Référence CVE CVE-2025-38180 https://www.cve.org/CVERecord?id=CVE-2025-38180 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40240 https://www.cve.org/CVERecord?id=CVE-2025-40240 Référence CVE CVE-2025-68811 https://www.cve.org/CVERecord?id=CVE-2025-68811 Référence CVE CVE-2025-71085 https://www.cve.org/CVERecord?id=CVE-2025-71085 Référence CVE CVE-2025-71238 https://www.cve.org/CVERecord?id=CVE-2025-71238 Référence CVE CVE-2026-23001 https://www.cve.org/CVERecord?id=CVE-2026-23001 Référence CVE CVE-2026-23111 https://www.cve.org/CVERecord?id=CVE-2026-23111 Référence CVE CVE-2026-23144 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2024-6923 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2025-12818 https://www.cve.org/CVERecord?id=CVE-2025-12818 Référence CVE CVE-2025-14847 https://www.cve.org/CVERecord?id=CVE-2025-14847 Référence CVE CVE-2025-24813 https://www.cve.org/CVERecord?id=CVE-2025-24813 Référence CVE CVE-2025-31650 https://www.cve.org/CVERecord?id=CVE-2025-31650 Référence CVE CVE-2025-31651 https://www.cve.org/CVERecord?id=CVE-2025-31651 Référence CVE CVE-2025-38129 https://www.cve.org/CVERecord?id=CVE-2025-38129 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-49124 https://www.cve.org/CVERecord?id=CVE-2025-49124 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-52434 https://www.cve.org/CVERecord?id=CVE-2025-52434 Référence CVE CVE-2025-52520 https://www.cve.org/CVERecord?id=CVE-2025-52520 Référence CVE CVE-2025-53506 https://www.cve.org/CVERecord?id=CVE-2025-53506 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55754 https://www.cve.org/CVERecord?id=CVE-2025-55754 Référence CVE CVE-2025-61795 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-40012 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40025 https://www.cve.org/CVERecord?id=CVE-2025-40025 Référence CVE CVE-2025-40032 https://www.cve.org/CVERecord?id=CVE-2025-40032 Référence CVE CVE-2025-40036 https://www.cve.org/CVERecord?id=CVE-2025-40036 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40054 https://www.cve.org/CVERecord?id=CVE-2025-40054 Référence CVE CVE-2025-40057 https://www.cve.org/CVERecord?id=CVE-2025-40057 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40073 https://www.cve.org/CVERecord?id=CVE-2025-40073 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40083 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-40012 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40025 https://www.cve.org/CVERecord?id=CVE-2025-40025 Référence CVE CVE-2025-40032 https://www.cve.org/CVERecord?id=CVE-2025-40032 Référence CVE CVE-2025-40036 https://www.cve.org/CVERecord?id=CVE-2025-40036 Référence CVE CVE-2025-40039 https://www.cve.org/CVERecord?id=CVE-2025-40039 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40054 https://www.cve.org/CVERecord?id=CVE-2025-40054 Référence CVE CVE-2025-40057 https://www.cve.org/CVERecord?id=CVE-2025-40057 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40073 https://www.cve.org/CVERecord?id=CVE-2025-40073 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40077 https://www.cve.org/CVERecord?id=CVE-2025-40077 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0290Multiples vulnérabilités dans le noyau Linux de Red Hat

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer une atteinte à l'intégrité des données, un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-40033 Référence CVE CVE-2025-40038 https://www.cve.org/CVERecord?id=CVE-2025-40038 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40045 https://www.cve.org/CVERecord?id=CVE-2025-40045 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0226Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2025-38106 Référence CVE CVE-2025-38129 https://www.cve.org/CVERecord?id=CVE-2025-38129 Référence CVE CVE-2025-38206 https://www.cve.org/CVERecord?id=CVE-2025-38206 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-38415 https://www.cve.org/CVERecord?id=CVE-2025-38415 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39933 https://www.cve.org/CVERecord?id=CVE-2025-39933 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-40269 https://www.cve.org/CVERecord?id=CVE-2025-40269 Référence CVE CVE-2025-40271 https://www.cve.org/CVERecord?id=CVE-2025-40271 Référence CVE CVE-2025-40304 https://www.cve.org/CVERecord?id=CVE-2025-40304 Référence CVE CVE-2025-40322 https://www.cve.org/CVERecord?id=CVE-2025-40322 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40033 Référence CVE CVE-2025-40038 https://www.cve.org/CVERecord?id=CVE-2025-40038 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40044 https://www.cve.org/CVERecord?id=CVE-2025-40044 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40097 https://www.cve.org/CVERecord?id=CVE-2025-40097 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40102 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-40055 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40057 https://www.cve.org/CVERecord?id=CVE-2025-40057 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40063 https://www.cve.org/CVERecord?id=CVE-2025-40063 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40065 https://www.cve.org/CVERecord?id=CVE-2025-40065 Référence CVE CVE-2025-40066 https://www.cve.org/CVERecord?id=CVE-2025-40066 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40069 https://www.cve.org/CVERecord?id=CVE-2025-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 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-40055 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40057 https://www.cve.org/CVERecord?id=CVE-2025-40057 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40063 https://www.cve.org/CVERecord?id=CVE-2025-40063 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40065 https://www.cve.org/CVERecord?id=CVE-2025-40065 Référence CVE CVE-2025-40066 https://www.cve.org/CVERecord?id=CVE-2025-40066 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40069 https://www.cve.org/CVERecord?id=CVE-2025-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 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-40055 Référence CVE CVE-2025-40056 https://www.cve.org/CVERecord?id=CVE-2025-40056 Référence CVE CVE-2025-40057 https://www.cve.org/CVERecord?id=CVE-2025-40057 Référence CVE CVE-2025-40058 https://www.cve.org/CVERecord?id=CVE-2025-40058 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40060 https://www.cve.org/CVERecord?id=CVE-2025-40060 Référence CVE CVE-2025-40061 https://www.cve.org/CVERecord?id=CVE-2025-40061 Référence CVE CVE-2025-40062 https://www.cve.org/CVERecord?id=CVE-2025-40062 Référence CVE CVE-2025-40063 https://www.cve.org/CVERecord?id=CVE-2025-40063 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40065 https://www.cve.org/CVERecord?id=CVE-2025-40065 Référence CVE CVE-2025-40066 https://www.cve.org/CVERecord?id=CVE-2025-40066 Référence CVE CVE-2025-40067 https://www.cve.org/CVERecord?id=CVE-2025-40067 Référence CVE CVE-2025-40068 https://www.cve.org/CVERecord?id=CVE-2025-40068 Référence CVE CVE-2025-40069 https://www.cve.org/CVERecord?id=CVE-2025-40069 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40071 https://www.cve.org/CVERecord?id=CVE-2025-40071 Référence CVE CVE-2025-40072 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39963 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=CVE-2025-39977 Référence CVE CVE-2025-40006 https://www.cve.org/CVERecord?id=CVE-2025-40006 Référence CVE CVE-2025-40019 https://www.cve.org/CVERecord?id=CVE-2025-40019 Référence CVE CVE-2025-40024 https://www.cve.org/CVERecord?id=CVE-2025-40024 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=CVE-2025-40033 Référence CVE CVE-2025-40035 https://www.cve.org/CVERecord?id=CVE-2025-40035 Référence CVE CVE-2025-40042 https://www.cve.org/CVERecord?id=CVE-2025-40042 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40102 https://www.cve.org/CVERecord?id=CVE-2025-40102 Référence CVE CVE-2025-40110 https://www.cve.org/CVERecord?id=CVE-2025-40110 Référence CVE CVE-2025-40123 https://www.cve.org/CVERecord?id=CVE-2025-40123 Référence CVE CVE-2025-40134 https://www.cve.org/CVERecord?id=CVE-2025-40134 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40031 Référence CVE CVE-2025-40033 https://www.cve.org/CVERecord?id=CVE-2025-40033 Référence CVE CVE-2025-40038 https://www.cve.org/CVERecord?id=CVE-2025-40038 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40047 https://www.cve.org/CVERecord?id=CVE-2025-40047 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40053 https://www.cve.org/CVERecord?id=CVE-2025-40053 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40081 https://www.cve.org/CVERecord?id=CVE-2025-40081 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40101 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40021 Référence CVE CVE-2025-40027 https://www.cve.org/CVERecord?id=CVE-2025-40027 Référence CVE CVE-2025-40030 https://www.cve.org/CVERecord?id=CVE-2025-40030 Référence CVE CVE-2025-40038 https://www.cve.org/CVERecord?id=CVE-2025-40038 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40047 https://www.cve.org/CVERecord?id=CVE-2025-40047 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40021 Référence CVE CVE-2025-40027 https://www.cve.org/CVERecord?id=CVE-2025-40027 Référence CVE CVE-2025-40030 https://www.cve.org/CVERecord?id=CVE-2025-40030 Référence CVE CVE-2025-40038 https://www.cve.org/CVERecord?id=CVE-2025-40038 Référence CVE CVE-2025-40040 https://www.cve.org/CVERecord?id=CVE-2025-40040 Référence CVE CVE-2025-40047 https://www.cve.org/CVERecord?id=CVE-2025-40047 Référence CVE CVE-2025-40048 https://www.cve.org/CVERecord?id=CVE-2025-40048 Référence CVE CVE-2025-40055 https://www.cve.org/CVERecord?id=CVE-2025-40055 Référence CVE CVE-2025-40059 https://www.cve.org/CVERecord?id=CVE-2025-40059 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40070 https://www.cve.org/CVERecord?id=CVE-2025-40070 Référence CVE CVE-2025-40074 https://www.cve.org/CVERecord?id=CVE-2025-40074 Référence CVE CVE-2025-40075 https://www.cve.org/CVERecord?id=CVE-2025-40075 Référence CVE CVE-2025-40080 https://www.cve.org/CVERecord?id=CVE-2025-40080 Référence CVE CVE-2025-40083 https://www.cve.org/CVERecord?id=CVE-2025-40083 Référence CVE CVE-2025-40086 https://www.cve.org/CVERecord?id=CVE-2025-40086 Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2025-40105 https://www.cve.org/CVERecord?id=

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

CVE-2025-40048 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40049 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40051 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40052 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40053 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40055 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40056 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40057 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40060 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40061 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40064 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40065 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40068 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40071 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40074 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40075 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40077 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40078 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40079 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40080 du 29 octobre 2025 Bulletin de sécurité Microsoft CVE-2025-40081

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
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 28 Oct 2025 · Last source change 2 Sept 2026, 12:49 UTC · CWE not yet assigned

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-36464
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Linux: 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79, 4.19 · Fixed: Linux: < 4.19, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
    After
    Linux: 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 005a7173d8e4710646043a681af36f79ce05a29b, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 302dbed4760bcd19a661cc1c282d91bb7481307e, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 08aca586482e88aab9616a3e81bc36cad22674a5, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79, 4.19 · Fixed: Linux: < 4.19, 6.1.187 ≤ 6.1.*, 6.6.156 ≤ 6.6.*, 6.12.108 ≤ 6.12.*, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
    CNA ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/005a7173d8e4710646043a681af36f79ce05a29b; removed remediation: git.kernel.org/233927b645cb7a14bb98d23ac72e4c7243a9f0d9.
    Before
    remediation: git.kernel.org/233927b645cb7a14bb98d23ac72e4c7243a9f0d9
    After
    remediation: git.kernel.org/005a7173d8e4710646043a681af36f79ce05a29b
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79; 4.19 · Fixed: < 4.19; 6.17.3 ≤ 6.17.*; 6.18 ≤ *
    After
    0afff91c6f5ecef27715ea71e34dc2baacba1060 < 005a7173d8e4710646043a681af36f79ce05a29b; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 302dbed4760bcd19a661cc1c282d91bb7481307e; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 08aca586482e88aab9616a3e81bc36cad22674a5; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79; 4.19 · Fixed: < 4.19; 6.1.187 ≤ 6.1.*; 6.6.156 ≤ 6.6.*; 6.12.108 ≤ 6.12.*; 6.17.3 ≤ 6.17.*; 6.18 ≤ *
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/233927b645cb7a14bb98d23ac72e4c7243a9f0d9; removed remediation: git.kernel.org/005a7173d8e4710646043a681af36f79ce05a29b.
    Before
    remediation: git.kernel.org/005a7173d8e4710646043a681af36f79ce05a29b
    After
    remediation: git.kernel.org/233927b645cb7a14bb98d23ac72e4c7243a9f0d9
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    0afff91c6f5ecef27715ea71e34dc2baacba1060 < 005a7173d8e4710646043a681af36f79ce05a29b; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 302dbed4760bcd19a661cc1c282d91bb7481307e; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 08aca586482e88aab9616a3e81bc36cad22674a5; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9; 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79; 4.19 · Fixed: < 4.19; 6.1.187 ≤ 6.1.*; 6.6.156 ≤ 6.6.*; 6.12.108 ≤ 6.12.*; 6.17.3 ≤ 6.17.*; 6.18 ≤ *
    After
    Linux: 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 233927b645cb7a14bb98d23ac72e4c7243a9f0d9, 0afff91c6f5ecef27715ea71e34dc2baacba1060 < 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79, 4.19 · Fixed: Linux: < 4.19, 6.17.3 ≤ 6.17.*, 6.18 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-36464↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor 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-40064 · cve.blacktree.nl