BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-22977High confidence

net: sock: fix hardened usercopy panic in sock_recv_errqueue

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

20 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-253495 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-253495: Multiple Vulnerabilities in SINEC OS before V4.0
1 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
Summary
In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719
Remediation
Update to V4.0 or later version
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2026-3682

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

What

In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → NULL Pointer Dereference → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-3682Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: sock: fix hardened usercopy panic in sock_recv_errqueue skbuff_fclone_cache was created without defining a usercopy region, [1] unlike skbuff_head_cache which properly whitelists the cb[] field. [2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is enabled and the kernel attempts to copy sk_buff.cb data to userspace via sock_recv_errqueue() -> put_cmsg(). The crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone() (from skbuff_fclone_cache) [1] 2. The skb is cloned via skb_clone() using the pre-allocated fclone [3] 3. The cloned skb is queued to sk_error_queue for timestamp reporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE) 5. sock_recv_errqueue() calls put_cmsg() to copy serr->ee from skb->cb [4] 6. __check_heap_object() fails because skbuff_fclone_cache has no usercopy whitelist [5] When cloned skbs allocated from skbuff_fclone_cache are used in the socket error queue, accessing the sock_exterr_skb structure in skb->cb via put_cmsg() triggers a usercopy hardening violation: [ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object 'skbuff_fclone_cache' (offset 296, size 16)! [ 5.382796] kernel BUG at mm/usercopy.c:102! [ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI [ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7 [ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 [ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80 [ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff <0f> 0b 490 [ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246 [ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74 [ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0 [ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74 [ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001 [ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00 [ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000 [ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0 [ 5.384903] PKRU: 55555554 [ 5.384903] Call Trace: [ 5.384903] <TASK> [ 5.384903] __check_heap_object+0x9a/0xd0 [ 5.384903] __check_object_size+0x46c/0x690 [ 5.384903] put_cmsg+0x129/0x5e0 [ 5.384903] sock_recv_errqueue+0x22f/0x380 [ 5.384903] tls_sw_recvmsg+0x7ed/0x1960 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? schedule+0x6d/0x270 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 [ 5.384903] ? mutex_unlock+0x81/0xd0 [ 5.384903] ? __pfx_mutex_unlock+0x10/0x10 [ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10 [ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0 [ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40 [ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5 The crash offset 296 corresponds to skb2->cb within skbuff_fclones: - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 - offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 = 272 + 24 (inside sock_exterr_skb.ee) This patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure. [1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885 [2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104 [3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566 [4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491 [5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719

Official EUVD record ↗
BSI · German · WID-SEC-2026-0194Linux Kernel: Schwachstelle ermöglicht Denial of Service

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

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

d?id=CVE-2025-71239 Référence CVE CVE-2025-71265 https://www.cve.org/CVERecord?id=CVE-2025-71265 Référence CVE CVE-2025-71266 https://www.cve.org/CVERecord?id=CVE-2025-71266 Référence CVE CVE-2025-71267 https://www.cve.org/CVERecord?id=CVE-2025-71267 Référence CVE CVE-2025-71274 https://www.cve.org/CVERecord?id=CVE-2025-71274 Référence CVE CVE-2025-71287 https://www.cve.org/CVERecord?id=CVE-2025-71287 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=CVE-2026-22986 Référence CVE CVE-2026-22987 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71288 Référence CVE CVE-2025-71291 https://www.cve.org/CVERecord?id=CVE-2025-71291 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71294 https://www.cve.org/CVERecord?id=CVE-2025-71294 Référence CVE CVE-2025-71295 https://www.cve.org/CVERecord?id=CVE-2025-71295 Référence CVE CVE-2025-71297 https://www.cve.org/CVERecord?id=CVE-2025-71297 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2025-71305 https://www.cve.org/CVERecord?id=CVE-2025-71305 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71266 Référence CVE CVE-2025-71267 https://www.cve.org/CVERecord?id=CVE-2025-71267 Référence CVE CVE-2025-71269 https://www.cve.org/CVERecord?id=CVE-2025-71269 Référence CVE CVE-2025-71274 https://www.cve.org/CVERecord?id=CVE-2025-71274 Référence CVE CVE-2025-71287 https://www.cve.org/CVERecord?id=CVE-2025-71287 Référence CVE CVE-2025-71288 https://www.cve.org/CVERecord?id=CVE-2025-71288 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=

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

025-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-23003, CVE-2026-23005, CVE-2026-23010, CVE-2026-23011, CVE-2026-23019, CVE-2026-23026, CVE-2026-23038, CVE-2026-23054, CVE-2026-23060, CVE-2026-23083, CVE-2026-23084, CVE-2026-23086, CVE-2026-23087, CVE-2026-23095, CVE-2026-23100, CVE-2026-23103, CVE-2026-23110, CVE-2026-23111, CVE-2026-23113, CVE-2026-23154, CVE-2026-23204, CVE-2026-23231, CVE-2026-23242, CVE-2026-23243, CVE-2026-23245, CVE-2026-23270, CVE-2026-23271, CVE-2026-23273, CVE-2026-23274, CVE-2026-23277, CVE-2026-23284, CVE-2026-23287, CVE-2026-23290, CVE-2026-23293, CVE-2026-23300, CVE-2026

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

d?id=CVE-2025-71286 Référence CVE CVE-2025-71291 https://www.cve.org/CVERecord?id=CVE-2025-71291 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71294 https://www.cve.org/CVERecord?id=CVE-2025-71294 Référence CVE CVE-2025-71295 https://www.cve.org/CVERecord?id=CVE-2025-71295 Référence CVE CVE-2025-71297 https://www.cve.org/CVERecord?id=CVE-2025-71297 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2025-71305 https://www.cve.org/CVERecord?id=CVE-2025-71305 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2025-71200 https://www.cve.org/CVERecord?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71186 Référence CVE CVE-2025-71188 https://www.cve.org/CVERecord?id=CVE-2025-71188 Référence CVE CVE-2025-71190 https://www.cve.org/CVERecord?id=CVE-2025-71190 Référence CVE CVE-2025-71191 https://www.cve.org/CVERecord?id=CVE-2025-71191 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71186 Référence CVE CVE-2025-71188 https://www.cve.org/CVERecord?id=CVE-2025-71188 Référence CVE CVE-2025-71190 https://www.cve.org/CVERecord?id=CVE-2025-71190 Référence CVE CVE-2025-71191 https://www.cve.org/CVERecord?id=CVE-2025-71191 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71186 Référence CVE CVE-2025-71188 https://www.cve.org/CVERecord?id=CVE-2025-71188 Référence CVE CVE-2025-71190 https://www.cve.org/CVERecord?id=CVE-2025-71190 Référence CVE CVE-2025-71191 https://www.cve.org/CVERecord?id=CVE-2025-71191 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-23019 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-23019 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-71225 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71231 https://www.cve.org/CVERecord?id=CVE-2025-71231 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71234 https://www.cve.org/CVERecord?id=CVE-2025-71234 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-7709 https://www.cve.org/CVERecord?id=CVE-2025-7709 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22988 https://www.cve.org/CVERecord?id=CVE-2026-22988 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=CVE-2026-22989 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71132 Référence CVE CVE-2025-71133 https://www.cve.org/CVERecord?id=CVE-2025-71133 Référence CVE CVE-2025-71136 https://www.cve.org/CVERecord?id=CVE-2025-71136 Référence CVE CVE-2025-71137 https://www.cve.org/CVERecord?id=CVE-2025-71137 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71180 https://www.cve.org/CVERecord?id=CVE-2025-71180 Référence CVE CVE-2025-71182 https://www.cve.org/CVERecord?id=CVE-2025-71182 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-23019 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2026-21637 Référence CVE CVE-2026-22185 https://www.cve.org/CVERecord?id=CVE-2026-22185 Référence CVE CVE-2026-2219 https://www.cve.org/CVERecord?id=CVE-2026-2219 Référence CVE CVE-2026-2243 https://www.cve.org/CVERecord?id=CVE-2026-2243 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-22860 https://www.cve.org/CVERecord?id=CVE-2026-22860 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2026-21637 Référence CVE CVE-2026-22185 https://www.cve.org/CVERecord?id=CVE-2026-22185 Référence CVE CVE-2026-2219 https://www.cve.org/CVERecord?id=CVE-2026-2219 Référence CVE CVE-2026-2243 https://www.cve.org/CVERecord?id=CVE-2026-2243 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-22860 https://www.cve.org/CVERecord?id=CVE-2026-22860 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71147 Référence CVE CVE-2025-71148 https://www.cve.org/CVERecord?id=CVE-2025-71148 Référence CVE CVE-2025-71149 https://www.cve.org/CVERecord?id=CVE-2025-71149 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71156 https://www.cve.org/CVERecord?id=CVE-2025-71156 Référence CVE CVE-2025-71157 https://www.cve.org/CVERecord?id=CVE-2025-71157 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=CVE-2026-22986 Référence CVE CVE-2026-22988 https://www.cve.org/CVERecord?id=CVE-2026-22988 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-71145 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71149 https://www.cve.org/CVERecord?id=CVE-2025-71149 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71156 https://www.cve.org/CVERecord?id=CVE-2025-71156 Référence CVE CVE-2025-71157 https://www.cve.org/CVERecord?id=CVE-2025-71157 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22988 https://www.cve.org/CVERecord?id=CVE-2026-22988 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22993 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71145 Référence CVE CVE-2025-71147 https://www.cve.org/CVERecord?id=CVE-2025-71147 Référence CVE CVE-2025-71149 https://www.cve.org/CVERecord?id=CVE-2025-71149 Référence CVE CVE-2025-71154 https://www.cve.org/CVERecord?id=CVE-2025-71154 Référence CVE CVE-2025-71156 https://www.cve.org/CVERecord?id=CVE-2025-71156 Référence CVE CVE-2025-71157 https://www.cve.org/CVERecord?id=CVE-2025-71157 Référence CVE CVE-2025-71162 https://www.cve.org/CVERecord?id=CVE-2025-71162 Référence CVE CVE-2025-71163 https://www.cve.org/CVERecord?id=CVE-2025-71163 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22988 https://www.cve.org/CVERecord?id=CVE-2026-22988 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22993 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71189 Référence CVE CVE-2025-71190 https://www.cve.org/CVERecord?id=CVE-2025-71190 Référence CVE CVE-2025-71191 https://www.cve.org/CVERecord?id=CVE-2025-71191 Référence CVE CVE-2025-71192 https://www.cve.org/CVERecord?id=CVE-2025-71192 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71192 Référence CVE CVE-2025-71193 https://www.cve.org/CVERecord?id=CVE-2025-71193 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71195 https://www.cve.org/CVERecord?id=CVE-2025-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=CVE-2026-22989 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-005644LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。net: sock: sock_recv_errqueueにおける強化されたusercopyパニックの修正です。skbuff_fclone_cacheはユーザーコピー領域を定義せずに作成されており、適切にcb[]フィールドをホワイトリストするskbuff_head_cacheとは異なります。そのため、CONFIG_HARDENED_USERCOPYが有効でカーネルがsock_recv_errqueue() - put_cmsg()経由でsk_buff.cbデータをユーザースペースにコピーしようとすると、usercopyのBUG()が発生します。クラッシュは次の条件で発生します。1.TCPがalloc_skb_fclone()（skbuff_fclone_cacheから）を使ってskbを割り当てる。2.skbがskb_clone()を使って事前割り当てされたfcloneでクローンされる。3.クローンされたskbがタイムスタンプ報告のためにsk_error_queueにキューされる。4.ユーザースペースがrecvmsg(MSG_ERRQUEUE)でエラーキューを読み取る。5.sock_recv_errqueue()がput_cmsg()を呼び、skb-cbからserr-eeをコピーする。6.__check_heap_object()が失敗する（skbuff_fclone_cacheにはusercopyホワイトリストがないため）。skbuff_fclone_cacheから割り当てられたクローンされたskbがソケットのエラーキューで使用されると、put_cmsg()経由でskb-cb内のsock_exterr_skb構造体にアクセスする際にusercopy強化違反が発生します。このパッチにより、強化されたusercopyチェック失敗を回避するためにローカルスタック変数をバウンスバッファとして使用しています。

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.
Patch available
Affected
Fixed
Linux: < 4.16, 5.10.248 ≤ 5.10.*, 5.15.198 ≤ 5.15.*, 6.1.161 ≤ 6.1.*, 6.6.121 ≤ 6.6.*, 6.12.66 ≤ 6.12.*, 6.18.6 ≤ 6.18.*, 6.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 21 Jan 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-3682
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

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

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-2026-3682↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-22977 · cve.blacktree.nl