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

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

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 10 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.

13 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 10 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.3.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.3.7-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.3.7-1Debian Security Tracker ↗Source updated 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

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

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler(). With Eric's ref tracker, syzbot finally found a repro for use-after-free in tcp_write_timer_handler() by kernel TCP sockets. [0] If SMC creates a kernel socket in __smc_create(), the kernel socket is supposed to be freed in smc_clcsock_release() by calling sock_release() when we close() the parent SMC socket. However, at the end of smc_clcsock_release(), the kernel socket's sk_state might not be TCP_CLOSE. This means that we have not called inet_csk_destroy_sock() in __tcp_close() and have not stopped the TCP timers. The kernel socket's TCP timers can be fired later, so we need to hold a refcnt for net as we do for MPTCP subflows in mptcp_subflow_create_socket(). [0]: leaked reference. sk_alloc (./include/net/net_namespace.h:335 net/core/sock.c:2108) inet_create (net/ipv4/af_inet.c:319 net/ipv4/af_inet.c:244) __sock_create (net/socket.c:1546) smc_create (net/smc/af_smc.c:3269 net/smc/af_smc.c:3284) __sock_create (net/socket.c:1546) __sys_socket (net/socket.c:1634 net/socket.c:1618 net/socket.c:1661) __x64_sys_socket (net/socket.c:1672) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) ================================================================== BUG: KASAN: slab-use-after-free in tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) Read of size 1 at addr ffff888052b65e0d by task syzrepro/18091 CPU: 0 PID: 18091 Comm: syzrepro Tainted: G W 6.3.0-rc4-01174-gb5d54eb5899a #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-1.amzn2022.0.1 04/01/2014 Call Trace: dump_stack_lvl (lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) kasan_report (mm/kasan/report.c:538) tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) tcp_write_timer (./include/linux/spinlock.h:390 net/ipv4/tcp_timer.c:643) call_timer_fn (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/timer.h:127 kernel/time/timer.c:1701) __run_timers.part.0 (kernel/time/timer.c:1752 kernel/time/timer.c:2022) run_timer_softirq (kernel/time/timer.c:2037) __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:572) __irq_exit_rcu (kernel/softirq.c:445 kernel/softirq.c:650) irq_exit_rcu (kernel/softirq.c:664) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1107 (discriminator 14))
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2023-60125

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler(). With Eric's ref tracker, syzbot finally found a repro for use-after-free in tcp_write_timer_handler() by kernel TCP sockets. [0] If SMC creates a kernel socket in __smc_create(), the kernel socket is supposed to be freed in smc_clcsock_release() by calling sock_release() when we close() the parent SMC socket. However, at the end of smc_clcsock_release(), the kernel socket's sk_state might not be TCP_CLOSE. This means that we have not called inet_csk_destroy_sock() in __tcp_close() and have not stopped the TCP timers. The kernel socket's TCP timers can be fired later, so we need to hold a refcnt for net as we do for MPTCP subflows in mptcp_subflow_create_socket(). [0]: leaked reference. sk_alloc (./include/net/net_namespace.h:335 net/core/sock.c:2108) inet_create (net/ipv4/af_inet.c:319 net/ipv4/af_inet.c:244) __sock_create (net/socket.c:1546) smc_create (net/smc/af_smc.c:3269 net/smc/af_smc.c:3284) __sock_create (net/socket.c:1546) __sys_socket (net/socket.c:1634 net/socket.c:1618 net/socket.c:1661) __x64_sys_socket (net/socket.c:1672) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) ================================================================== BUG: KASAN: slab-use-after-free in tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) Read of size 1 at addr ffff888052b65e0d by task syzrepro/18091 CPU: 0 PID: 18091 Comm: syzrepro Tainted: G W 6.3.0-rc4-01174-gb5d54eb5899a #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-1.amzn2022.0.1 04/01/2014 Call Trace: <IRQ> dump_stack_lvl (lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) kasan_report (mm/kasan/report.c:538) tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) tcp_write_timer (./include/linux/spinlock.h:390 net/ipv4/tcp_timer.c:643) call_timer_fn (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/timer.h:127 kernel/time/timer.c:1701) __run_timers.part.0 (kernel/time/timer.c:1752 kernel/time/timer.c:2022) run_timer_softirq (kernel/time/timer.c:2037) __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:572) __irq_exit_rcu (kernel/softirq.c:445 kernel/softirq.c:650) irq_exit_rcu (kernel/softirq.c:664) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1107 (discriminator 14)) </IRQ>

What

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler(). With Eric's ref tracker, syzbot finally found a repro for use-after-free in tcp_write_timer_handler() by kernel TCP sockets. [0] If SMC creates a kernel socket in __smc_create(), the kernel socket is supposed to be freed in smc_clcsock_release() by calling sock_release() when we close() the parent SMC socket. However, at the end of smc_clcsock_release(), the kernel socket's sk_state might not be TCP_CLOSE. This means that we have not called inet_csk_destroy_sock() in __tcp_close() and have not stopped the TCP timers. The kernel socket's TCP timers can be fired later, so we need to hold a refcnt for net as we do for MPTCP subflows in mptcp_subflow_create_socket(). [0]: leaked reference. sk_alloc (./include/net/net_namespace.h:335 net/core/sock.c:2108) inet_create (net/ipv4/af_inet.c:319 net/ipv4/af_inet.c:244) __sock_create (net/socket.c:1546) smc_create (net/smc/af_smc.c:3269 net/smc/af_smc.c:3284) __sock_create (net/socket.c:1546) __sys_socket (net/socket.c:1634 net/socket.c:1618 net/socket.c:1661) __x64_sys_socket (net/socket.c:1672) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) ================================================================== BUG: KASAN: slab-use-after-free in tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) Read of size 1 at addr ffff888052b65e0d by task syzrepro/18091 CPU: 0 PID: 18091 Comm: syzrepro Tainted: G W 6.3.0-rc4-01174-gb5d54eb5899a #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-1.amzn2022.0.1 04/01/2014 Call Trace: <IRQ> dump_stack_lvl (lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) kasan_report (mm/kasan/report.c:538) tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) tcp_write_timer (./include/linux/spinlock.h:390 net/ipv4/tcp_timer.c:643) call_timer_fn (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/timer.h:127 kernel/time/timer.c:1701) __run_timers.part.0 (kernel/time/timer.c:1752 kernel/time/timer.c:2022) run_timer_softirq (kernel/time/timer.c:2037) __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:572) __irq_exit_rcu (kernel/softirq.c:445 kernel/softirq.c:650) irq_exit_rcu (kernel/softirq.c:664) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1107 (discriminator 14)) </IRQ>

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in tcp_write_timer_handler(). With Eric's ref tracker, syzbot finally found a repro for use-after-free in tcp_write_timer_handler() by kernel TCP sockets. [0] If SMC creates a kernel socket in __smc_create(), the kernel socket is supposed to be freed in smc_clcsock_release() by calling sock_release() when we close() the parent SMC socket. However, at the end of smc_clcsock_release(), the kernel socket's sk_state might not be TCP_CLOSE. This means that we have not called inet_csk_destroy_sock() in __tcp_close() and have not stopped the TCP timers. The kernel socket's TCP timers can be fired later, so we need to hold a refcnt for net as we do for MPTCP subflows in mptcp_subflow_create_socket(). [0]: leaked reference. sk_alloc (./include/net/net_namespace.h:335 net/core/sock.c:2108) inet_create (net/ipv4/af_inet.c:319 net/ipv4/af_inet.c:244) __sock_create (net/socket.c:1546) smc_create (net/smc/af_smc.c:3269 net/smc/af_smc.c:3284) __sock_create (net/socket.c:1546) __sys_socket (net/socket.c:1634 net/socket.c:1618 net/socket.c:1661) __x64_sys_socket (net/socket.c:1672) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) ================================================================== BUG: KASAN: slab-use-after-free in tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) Read of size 1 at addr ffff888052b65e0d by task syzrepro/18091 CPU: 0 PID: 18091 Comm: syzrepro Tainted: G W 6.3.0-rc4-01174-gb5d54eb5899a #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-1.amzn2022.0.1 04/01/2014 Call Trace: <IRQ> dump_stack_lvl (lib/dump_stack.c:107) print_report (mm/kasan/report.c:320 mm/kasan/report.c:430) kasan_report (mm/kasan/report.c:538) tcp_write_timer_handler (net/ipv4/tcp_timer.c:378 net/ipv4/tcp_timer.c:624 net/ipv4/tcp_timer.c:594) tcp_write_timer (./include/linux/spinlock.h:390 net/ipv4/tcp_timer.c:643) call_timer_fn (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/timer.h:127 kernel/time/timer.c:1701) __run_timers.part.0 (kernel/time/timer.c:1752 kernel/time/timer.c:2022) run_timer_softirq (kernel/time/timer.c:2037) __do_softirq (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:207 ./include/trace/events/irq.h:142 kernel/softirq.c:572) __irq_exit_rcu (kernel/softirq.c:445 kernel/softirq.c:650) irq_exit_rcu (kernel/softirq.c:664) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1107 (discriminator 14)) </IRQ>

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2765Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251210Security Bulletin 10 Dec 2025

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

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

tembre 2026 https://access.redhat.com/errata/RHSA-2026:71601 Bulletin de sécurité Red Hat RHSA-2026:71606 du 24 septembre 2026 https://access.redhat.com/errata/RHSA-2026:71606 Bulletin de sécurité Red Hat RHSA-2026:71649 du 24 septembre 2026 https://access.redhat.com/errata/RHSA-2026:71649 Bulletin de sécurité Red Hat RHSA-2026:71657 du 24 septembre 2026 https://access.redhat.com/errata/RHSA-2026:71657 Bulletin de sécurité Red Hat RHSA-2026:71687 du 24 septembre 2026 https://access.redhat.com/errata/RHSA-2026:71687 Bulletin de sécurité Red Hat RHSA-2026:71700 du 25 septembre 2026 https://access.redhat.com/errata/RHSA-2026:71700 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-54120 https://www.cve.org/CVERecord?id=CVE-2023-54120 Référence CVE CVE-2023-54214 https://www.cve.org/CVERecord?id=CVE-2023-54214 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-71082 https://www.cve.org/CVERecord?id=CVE-2025-71082 Référence CVE CVE-2026-23007 https://www.cve.org/CVERecord?id=CVE-2026-23007 Référence CVE CVE-2026-31539 https://www.cve.org/CVERecord?id=

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

05 août 2026 https://www.ibm.com/support/pages/node/7282667 Bulletin de sécurité IBM 7282819 du 07 août 2026 https://www.ibm.com/support/pages/node/7282819 Bulletin de sécurité IBM 7282820 du 07 août 2026 https://www.ibm.com/support/pages/node/7282820 Bulletin de sécurité IBM 7282821 du 07 août 2026 https://www.ibm.com/support/pages/node/7282821 Bulletin de sécurité IBM 7282822 du 07 août 2026 https://www.ibm.com/support/pages/node/7282822 Bulletin de sécurité IBM 7282827 du 07 août 2026 https://www.ibm.com/support/pages/node/7282827 Bulletin de sécurité IBM 7282829 du 07 août 2026 https://www.ibm.com/support/pages/node/7282829 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2024-34459 https://www.cve.org/CVERecord?id=CVE-2024-34459 Référence CVE CVE-2024-4741 https://www.cve.org/CVERecord?id=CVE-2024-4741 Référence CVE CVE-2025-13755 https://www.cve.org/CVERecord?id=CVE-2025-13755 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-36372 https://www.cve.org/CVERecord?id=CVE-2025-36372 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-53906 https://www.cve.org/CVERecord?id=CV

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

Hat RHSA-2026:25095 du 10 juin 2026 https://access.redhat.com/errata/RHSA-2026:25095 Bulletin de sécurité Red Hat RHSA-2026:25120 du 10 juin 2026 https://access.redhat.com/errata/RHSA-2026:25120 Bulletin de sécurité Red Hat RHSA-2026:25121 du 10 juin 2026 https://access.redhat.com/errata/RHSA-2026:25121 Bulletin de sécurité Red Hat RHSA-2026:25191 du 11 juin 2026 https://access.redhat.com/errata/RHSA-2026:25191 Bulletin de sécurité Red Hat RHSA-2026:25217 du 11 juin 2026 https://access.redhat.com/errata/RHSA-2026:25217 Bulletin de sécurité Red Hat RHSA-2026:25218 du 11 juin 2026 https://access.redhat.com/errata/RHSA-2026:25218 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40158 https://www.cve.org/CVERecord?id=CVE-2025-40158 Référence CVE CVE-2025-40170 https://www.cve.org/CVERecord?id=CVE-2025-40170 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53743 Référence CVE CVE-2023-53750 https://www.cve.org/CVERecord?id=CVE-2023-53750 Référence CVE CVE-2023-53752 https://www.cve.org/CVERecord?id=CVE-2023-53752 Référence CVE CVE-2023-53759 https://www.cve.org/CVERecord?id=CVE-2023-53759 Référence CVE CVE-2023-53762 https://www.cve.org/CVERecord?id=CVE-2023-53762 Référence CVE CVE-2023-53766 https://www.cve.org/CVERecord?id=CVE-2023-53766 Référence CVE CVE-2023-53768 https://www.cve.org/CVERecord?id=CVE-2023-53768 Référence CVE CVE-2023-53777 https://www.cve.org/CVERecord?id=CVE-2023-53777 Référence CVE CVE-2023-53778 https://www.cve.org/CVERecord?id=CVE-2023-53778 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53782 https://www.cve.org/CVERecord?id=CVE-2023-53782 Référence CVE CVE-2023-53784 https://www.cve.org/CVERecord?id=CVE-2023-53784 Référence CVE CVE-2023-53785 https://www.cve.org/CVERecord?id=CVE-2023-53785 Référence CVE CVE-2023-53787 https://www.cve.org/CVERecord?id=CVE-2023-53787 Référence CVE CVE-2023-53791 https://www.cve.org/CVERecord?id=CVE-2023-53791 Référence CVE CVE-2023-53792 https://www.cve.org/CVERecord?id=CVE-2023-53792 Référence CVE CVE-2023-53793 https://www.cve.org/CVERecord?id=CVE-2023-53793 Référence CVE CVE-2023-53794 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53742 Référence CVE CVE-2023-53743 https://www.cve.org/CVERecord?id=CVE-2023-53743 Référence CVE CVE-2023-53748 https://www.cve.org/CVERecord?id=CVE-2023-53748 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2023-53753 https://www.cve.org/CVERecord?id=CVE-2023-53753 Référence CVE CVE-2023-53764 https://www.cve.org/CVERecord?id=CVE-2023-53764 Référence CVE CVE-2023-53765 https://www.cve.org/CVERecord?id=CVE-2023-53765 Référence CVE CVE-2023-53767 https://www.cve.org/CVERecord?id=CVE-2023-53767 Référence CVE CVE-2023-53780 https://www.cve.org/CVERecord?id=CVE-2023-53780 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53785 https://www.cve.org/CVERecord?id=CVE-2023-53785 Référence CVE CVE-2023-53789 https://www.cve.org/CVERecord?id=CVE-2023-53789 Référence CVE CVE-2023-53791 https://www.cve.org/CVERecord?id=CVE-2023-53791 Référence CVE CVE-2023-53794 https://www.cve.org/CVERecord?id=CVE-2023-53794 Référence CVE CVE-2023-53806 https://www.cve.org/CVERecord?id=CVE-2023-53806 Référence CVE CVE-2023-53816 https://www.cve.org/CVERecord?id=CVE-2023-53816 Référence CVE CVE-2023-53822 https://www.cve.org/CVERecord?id=CVE-2023-53822 Référence CVE CVE-2023-53829 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53742 Référence CVE CVE-2023-53743 https://www.cve.org/CVERecord?id=CVE-2023-53743 Référence CVE CVE-2023-53748 https://www.cve.org/CVERecord?id=CVE-2023-53748 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2023-53753 https://www.cve.org/CVERecord?id=CVE-2023-53753 Référence CVE CVE-2023-53764 https://www.cve.org/CVERecord?id=CVE-2023-53764 Référence CVE CVE-2023-53765 https://www.cve.org/CVERecord?id=CVE-2023-53765 Référence CVE CVE-2023-53767 https://www.cve.org/CVERecord?id=CVE-2023-53767 Référence CVE CVE-2023-53780 https://www.cve.org/CVERecord?id=CVE-2023-53780 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53785 https://www.cve.org/CVERecord?id=CVE-2023-53785 Référence CVE CVE-2023-53789 https://www.cve.org/CVERecord?id=CVE-2023-53789 Référence CVE CVE-2023-53791 https://www.cve.org/CVERecord?id=CVE-2023-53791 Référence CVE CVE-2023-53794 https://www.cve.org/CVERecord?id=CVE-2023-53794 Référence CVE CVE-2023-53806 https://www.cve.org/CVERecord?id=CVE-2023-53806 Référence CVE CVE-2023-53816 https://www.cve.org/CVERecord?id=CVE-2023-53816 Référence CVE CVE-2023-53822 https://www.cve.org/CVERecord?id=CVE-2023-53822 Référence CVE CVE-2023-53829 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53754 Référence CVE CVE-2023-53755 https://www.cve.org/CVERecord?id=CVE-2023-53755 Référence CVE CVE-2023-53759 https://www.cve.org/CVERecord?id=CVE-2023-53759 Référence CVE CVE-2023-53761 https://www.cve.org/CVERecord?id=CVE-2023-53761 Référence CVE CVE-2023-53762 https://www.cve.org/CVERecord?id=CVE-2023-53762 Référence CVE CVE-2023-53766 https://www.cve.org/CVERecord?id=CVE-2023-53766 Référence CVE CVE-2023-53768 https://www.cve.org/CVERecord?id=CVE-2023-53768 Référence CVE CVE-2023-53777 https://www.cve.org/CVERecord?id=CVE-2023-53777 Référence CVE CVE-2023-53778 https://www.cve.org/CVERecord?id=CVE-2023-53778 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53782 https://www.cve.org/CVERecord?id=CVE-2023-53782 Référence CVE CVE-2023-53783 https://www.cve.org/CVERecord?id=CVE-2023-53783 Référence CVE CVE-2023-53784 https://www.cve.org/CVERecord?id=CVE-2023-53784 Référence CVE CVE-2023-53785 https://www.cve.org/CVERecord?id=CVE-2023-53785 Référence CVE CVE-2023-53786 https://www.cve.org/CVERecord?id=CVE-2023-53786 Référence CVE CVE-2023-53787 https://www.cve.org/CVERecord?id=CVE-2023-53787 Référence CVE CVE-2023-53788 https://www.cve.org/CVERecord?id=CVE-2023-53788 Référence CVE CVE-2023-53791 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-2023-53743 Référence CVE CVE-2023-53744 https://www.cve.org/CVERecord?id=CVE-2023-53744 Référence CVE CVE-2023-53746 https://www.cve.org/CVERecord?id=CVE-2023-53746 Référence CVE CVE-2023-53747 https://www.cve.org/CVERecord?id=CVE-2023-53747 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2023-53754 https://www.cve.org/CVERecord?id=CVE-2023-53754 Référence CVE CVE-2023-53755 https://www.cve.org/CVERecord?id=CVE-2023-53755 Référence CVE CVE-2023-53761 https://www.cve.org/CVERecord?id=CVE-2023-53761 Référence CVE CVE-2023-53766 https://www.cve.org/CVERecord?id=CVE-2023-53766 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53783 https://www.cve.org/CVERecord?id=CVE-2023-53783 Référence CVE CVE-2023-53786 https://www.cve.org/CVERecord?id=CVE-2023-53786 Référence CVE CVE-2023-53788 https://www.cve.org/CVERecord?id=CVE-2023-53788 Référence CVE CVE-2023-53792 https://www.cve.org/CVERecord?id=CVE-2023-53792 Référence CVE CVE-2023-53794 https://www.cve.org/CVERecord?id=CVE-2023-53794 Référence CVE CVE-2023-53802 https://www.cve.org/CVERecord?id=CVE-2023-53802 Référence CVE CVE-2023-53803 https://www.cve.org/CVERecord?id=CVE-2023-53803 Référence CVE CVE-2023-53804 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2022-50876 Référence CVE CVE-2022-50880 https://www.cve.org/CVERecord?id=CVE-2022-50880 Référence CVE CVE-2022-50884 https://www.cve.org/CVERecord?id=CVE-2022-50884 Référence CVE CVE-2022-50889 https://www.cve.org/CVERecord?id=CVE-2022-50889 Référence CVE CVE-2023-23559 https://www.cve.org/CVERecord?id=CVE-2023-23559 Référence CVE CVE-2023-4132 https://www.cve.org/CVERecord?id=CVE-2023-4132 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53254 https://www.cve.org/CVERecord?id=CVE-2023-53254 Référence CVE CVE-2023-53761 https://www.cve.org/CVERecord?id=CVE-2023-53761 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-54019 https://www.cve.org/CVERecord?id=CVE-2023-54019 Référence CVE CVE-2023-54024 https://www.cve.org/CVERecord?id=CVE-2023-54024 Référence CVE CVE-2023-54110 https://www.cve.org/CVERecord?id=CVE-2023-54110 Référence CVE CVE-2023-54142 https://www.cve.org/CVERecord?id=CVE-2023-54142 Référence CVE CVE-2023-54168 https://www.cve.org/CVERecord?id=CVE-2023-54168 Référence CVE CVE-2023-54170 https://www.cve.org/CVERecord?id=CVE-2023-54170 Référence CVE CVE-2023-54242 https://www.cve.org/CVERecord?id=CVE-2023-54242 Référence CVE CVE-2023-54243 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-2023-53761 Référence CVE CVE-2023-53762 https://www.cve.org/CVERecord?id=CVE-2023-53762 Référence CVE CVE-2023-53765 https://www.cve.org/CVERecord?id=CVE-2023-53765 Référence CVE CVE-2023-53766 https://www.cve.org/CVERecord?id=CVE-2023-53766 Référence CVE CVE-2023-53768 https://www.cve.org/CVERecord?id=CVE-2023-53768 Référence CVE CVE-2023-53769 https://www.cve.org/CVERecord?id=CVE-2023-53769 Référence CVE CVE-2023-53777 https://www.cve.org/CVERecord?id=CVE-2023-53777 Référence CVE CVE-2023-53778 https://www.cve.org/CVERecord?id=CVE-2023-53778 Référence CVE CVE-2023-53780 https://www.cve.org/CVERecord?id=CVE-2023-53780 Référence CVE CVE-2023-53781 https://www.cve.org/CVERecord?id=CVE-2023-53781 Référence CVE CVE-2023-53782 https://www.cve.org/CVERecord?id=CVE-2023-53782 Référence CVE CVE-2023-53783 https://www.cve.org/CVERecord?id=CVE-2023-53783 Référence CVE CVE-2023-53784 https://www.cve.org/CVERecord?id=CVE-2023-53784 Référence CVE CVE-2023-53785 https://www.cve.org/CVERecord?id=CVE-2023-53785 Référence CVE CVE-2023-53786 https://www.cve.org/CVERecord?id=CVE-2023-53786 Référence CVE CVE-2023-53787 https://www.cve.org/CVERecord?id=CVE-2023-53787 Référence CVE CVE-2023-53788 https://www.cve.org/CVERecord?id=CVE-2023-53788 Référence CVE CVE-2023-53791 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
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 9 Dec 2025 · Last source change 5 Aug 2026, 09:15 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-60125
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗

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