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

net/smc: fix general protection fault in __smc_diag_dump

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 13 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% 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: Manual assessmentRemediation target: Manual assessment

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 13 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.

17 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 13 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.57-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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 archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-203630

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

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 13 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: net/smc: fix general protection fault in __smc_diag_dump The syzbot report a crash: Oops: general protection fault, probably for non-canonical address 0xfbd5a5d5a0000003: 0000 [#1] SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdead4ead00000018-0xdead4ead0000001f] CPU: 1 UID: 0 PID: 6949 Comm: syz.0.335 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:smc_diag_msg_common_fill net/smc/smc_diag.c:44 [inline] RIP: 0010:__smc_diag_dump.constprop.0+0x3ca/0x2550 net/smc/smc_diag.c:89 Call Trace: <TASK> smc_diag_dump_proto+0x26d/0x420 net/smc/smc_diag.c:217 smc_diag_dump+0x27/0x90 net/smc/smc_diag.c:234 netlink_dump+0x539/0xd30 net/netlink/af_netlink.c:2327 __netlink_dump_start+0x6d6/0x990 net/netlink/af_netlink.c:2442 netlink_dump_start include/linux/netlink.h:341 [inline] smc_diag_handler_dump+0x1f9/0x240 net/smc/smc_diag.c:251 __sock_diag_cmd net/core/sock_diag.c:249 [inline] sock_diag_rcv_msg+0x438/0x790 net/core/sock_diag.c:285 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5a7/0x870 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg net/socket.c:729 [inline] ____sys_sendmsg+0xa95/0xc70 net/socket.c:2614 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2668 __sys_sendmsg+0x16d/0x220 net/socket.c:2700 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> The process like this: (CPU1) | (CPU2) ---------------------------------|------------------------------- inet_create() | // init clcsock to NULL | sk = sk_alloc() | | // unexpectedly change clcsock | inet_init_csk_locks() | | // add sk to hash table | smc_inet_init_sock() | smc_sk_init() | smc_hash_sk() | | // traverse the hash table | smc_diag_dump_proto | __smc_diag_dump() | // visit wrong clcsock | smc_diag_msg_common_fill() // alloc clcsock | smc_create_clcsk | sock_create_kern | With CONFIG_DEBUG_LOCK_ALLOC=y, the smc->clcsock is unexpectedly changed in inet_init_csk_locks(). The INET_PROTOSW_ICSK flag is no need by smc, just remove it. After removing the INET_PROTOSW_ICSK flag, this patch alse revert commit 6fd27ea183c2 ("net/smc: fix lacks of icsk_syn_mss with IPPROTO_SMC") to avoid casting smc_sock to inet_connection_sock.

What

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix general protection fault in __smc_diag_dump The syzbot report a crash: Oops: general protection fault, probably for non-canonical address 0xfbd5a5d5a0000003: 0000 [#1] SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdead4ead00000018-0xdead4ead0000001f] CPU: 1 UID: 0 PID: 6949 Comm: syz.0.335 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:smc_diag_msg_common_fill net/smc/smc_diag.c:44 [inline] RIP: 0010:__smc_diag_dump.constprop.0+0x3ca/0x2550 net/smc/smc_diag.c:89 Call Trace: <TASK> smc_diag_dump_proto+0x26d/0x420 net/smc/smc_diag.c:217 smc_diag_dump+0x27/0x90 net/smc/smc_diag.c:234 netlink_dump+0x539/0xd30 net/netlink/af_netlink.c:2327 __netlink_dump_start+0x6d6/0x990 net/netlink/af_netlink.c:2442 netlink_dump_start include/linux/netlink.h:341 [inline] smc_diag_handler_dump+0x1f9/0x240 net/smc/smc_diag.c:251 __sock_diag_cmd net/core/sock_diag.c:249 [inline] sock_diag_rcv_msg+0x438/0x790 net/core/sock_diag.c:285 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5a7/0x870 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg net/socket.c:729 [inline] ____sys_sendmsg+0xa95/0xc70 net/socket.c:2614 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2668 __sys_sendmsg+0x16d/0x220 net/socket.c:2700 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> The process like this: (CPU1) | (CPU2) ---------------------------------|------------------------------- inet_create() | // init clcsock to NULL | sk = sk_alloc() | | // unexpectedly change clcsock | inet_init_csk_locks() | | // add sk to hash table | smc_inet_init_sock() | smc_sk_init() | smc_hash_sk() | | // traverse the hash table | smc_diag_dump_proto | __smc_diag_dump() | // visit wrong clcsock | smc_diag_msg_common_fill() // alloc clcsock | smc_create_clcsk | sock_create_kern | With CONFIG_DEBUG_LOCK_ALLOC=y, the smc->clcsock is unexpectedly changed in inet_init_csk_locks(). The INET_PROTOSW_ICSK flag is no need by smc, just remove it. After removing the INET_PROTOSW_ICSK flag, this patch alse revert commit 6fd27ea183c2 ("net/smc: fix lacks of icsk_syn_mss with IPPROTO_SMC") to avoid casting smc_sock to inet_connection_sock.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix general protection fault in __smc_diag_dump The syzbot report a crash: Oops: general protection fault, probably for non-canonical address 0xfbd5a5d5a0000003: 0000 [#1] SMP KASAN NOPTI KASAN: maybe wild-memory-access in range [0xdead4ead00000018-0xdead4ead0000001f] CPU: 1 UID: 0 PID: 6949 Comm: syz.0.335 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 RIP: 0010:smc_diag_msg_common_fill net/smc/smc_diag.c:44 [inline] RIP: 0010:__smc_diag_dump.constprop.0+0x3ca/0x2550 net/smc/smc_diag.c:89 Call Trace: <TASK> smc_diag_dump_proto+0x26d/0x420 net/smc/smc_diag.c:217 smc_diag_dump+0x27/0x90 net/smc/smc_diag.c:234 netlink_dump+0x539/0xd30 net/netlink/af_netlink.c:2327 __netlink_dump_start+0x6d6/0x990 net/netlink/af_netlink.c:2442 netlink_dump_start include/linux/netlink.h:341 [inline] smc_diag_handler_dump+0x1f9/0x240 net/smc/smc_diag.c:251 __sock_diag_cmd net/core/sock_diag.c:249 [inline] sock_diag_rcv_msg+0x438/0x790 net/core/sock_diag.c:285 netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552 netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline] netlink_unicast+0x5a7/0x870 net/netlink/af_netlink.c:1346 netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1896 sock_sendmsg_nosec net/socket.c:714 [inline] __sock_sendmsg net/socket.c:729 [inline] ____sys_sendmsg+0xa95/0xc70 net/socket.c:2614 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2668 __sys_sendmsg+0x16d/0x220 net/socket.c:2700 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4e0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f </TASK> The process like this: (CPU1) | (CPU2) ---------------------------------|------------------------------- inet_create() | // init clcsock to NULL | sk = sk_alloc() | | // unexpectedly change clcsock | inet_init_csk_locks() | | // add sk to hash table | smc_inet_init_sock() | smc_sk_init() | smc_hash_sk() | | // traverse the hash table | smc_diag_dump_proto | __smc_diag_dump() | // visit wrong clcsock | smc_diag_msg_common_fill() // alloc clcsock | smc_create_clcsk | sock_create_kern | With CONFIG_DEBUG_LOCK_ALLOC=y, the smc->clcsock is unexpectedly changed in inet_init_csk_locks(). The INET_PROTOSW_ICSK flag is no need by smc, just remove it. After removing the INET_PROTOSW_ICSK flag, this patch alse revert commit 6fd27ea183c2 ("net/smc: fix lacks of icsk_syn_mss with IPPROTO_SMC") to avoid casting smc_sock to inet_connection_sock.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

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
the affected interface → vulnerable operation → disrupt the affected service
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
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.
Denial of service
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

d?id=CVE-2025-40347 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40350 https://www.cve.org/CVERecord?id=CVE-2025-40350 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-40352 https://www.cve.org/CVERecord?id=CVE-2025-40352 Référence CVE CVE-2025-40353 https://www.cve.org/CVERecord?id=CVE-2025-40353 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40357 https://www.cve.org/CVERecord?id=CVE-2025-40357 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40359 https://www.cve.org/CVERecord?id=CVE-2025-40359 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 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-40347 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40350 https://www.cve.org/CVERecord?id=CVE-2025-40350 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-40352 https://www.cve.org/CVERecord?id=CVE-2025-40352 Référence CVE CVE-2025-40353 https://www.cve.org/CVERecord?id=CVE-2025-40353 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40357 https://www.cve.org/CVERecord?id=CVE-2025-40357 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40359 https://www.cve.org/CVERecord?id=CVE-2025-40359 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 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-40347 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40350 https://www.cve.org/CVERecord?id=CVE-2025-40350 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-40352 https://www.cve.org/CVERecord?id=CVE-2025-40352 Référence CVE CVE-2025-40353 https://www.cve.org/CVERecord?id=CVE-2025-40353 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40357 https://www.cve.org/CVERecord?id=CVE-2025-40357 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40359 https://www.cve.org/CVERecord?id=CVE-2025-40359 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68169 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-40343 Référence CVE CVE-2025-40344 https://www.cve.org/CVERecord?id=CVE-2025-40344 Référence CVE CVE-2025-40345 https://www.cve.org/CVERecord?id=CVE-2025-40345 Référence CVE CVE-2025-40346 https://www.cve.org/CVERecord?id=CVE-2025-40346 Référence CVE CVE-2025-40347 https://www.cve.org/CVERecord?id=CVE-2025-40347 Référence CVE CVE-2025-40350 https://www.cve.org/CVERecord?id=CVE-2025-40350 Référence CVE CVE-2025-40353 https://www.cve.org/CVERecord?id=CVE-2025-40353 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40357 https://www.cve.org/CVERecord?id=CVE-2025-40357 Référence CVE CVE-2025-40359 https://www.cve.org/CVERecord?id=CVE-2025-40359 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-68167 https://www.cve.org/CVERecord?id=CVE-2025-68167 Référence CVE CVE-2025-68170 https://www.cve.org/CVERecord?id=CVE-2025-68170 Référence CVE CVE-2025-68171 https://www.cve.org/CVERecord?id=CVE-2025-68171 Référence CVE CVE-2025-68172 https://www.cve.org/CVERecord?id=CVE-2025-68172 Référence CVE CVE-2025-68176 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-40340 Référence CVE CVE-2025-40342 https://www.cve.org/CVERecord?id=CVE-2025-40342 Référence CVE CVE-2025-40343 https://www.cve.org/CVERecord?id=CVE-2025-40343 Référence CVE CVE-2025-40345 https://www.cve.org/CVERecord?id=CVE-2025-40345 Référence CVE CVE-2025-40346 https://www.cve.org/CVERecord?id=CVE-2025-40346 Référence CVE CVE-2025-40347 https://www.cve.org/CVERecord?id=CVE-2025-40347 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-40354 https://www.cve.org/CVERecord?id=CVE-2025-40354 Référence CVE CVE-2025-40357 https://www.cve.org/CVERecord?id=CVE-2025-40357 Référence CVE CVE-2025-40359 https://www.cve.org/CVERecord?id=CVE-2025-40359 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-68168 https://www.cve.org/CVERecord?id=CVE-2025-68168 Référence CVE CVE-2025-68170 https://www.cve.org/CVERecord?id=CVE-2025-68170 Référence CVE CVE-2025-68172 https://www.cve.org/CVERecord?id=CVE-2025-68172 Référence CVE CVE-2025-68176 https://www.cve.org/CVERecord?id=CVE-2025-68176 Référence CVE CVE-2025-68180 https://www.cve.org/CVERecord?id=CVE-2025-68180 Référence CVE CVE-2025-68181 https://www.cve.org/CVERecord?id=

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
Linux: d25a92ccae6bed02327b63d138e12e7806830f78 < 5b6fc95c4a161326567bdf12a333768565b638f2, d25a92ccae6bed02327b63d138e12e7806830f78 < 99b5b3faf3220ba1cdab8e6e42be4f3f993937c3, d25a92ccae6bed02327b63d138e12e7806830f78 < f584239a9ed25057496bf397c370cc5163dde419, 6.11
Fixed
Linux: < 6.11, 6.12.56 ≤ 6.12.*, 6.17.6 ≤ 6.17.*, 6.18 ≤ *
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 16 Dec 2025 · Last source change 11 May 2026, 21:47 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-203630
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗

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

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