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

tcp: call sk_data_ready() after listener migration

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 25 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 25 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.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

3 current
CVE-2026-46015 · CSAF 2.0 · revision 19 · interimSUSE Product Security TeamCVE-2026-46015
180 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-46015 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: tcp: call sk_data_ready() after listener migration
36 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's TCP networking subsystem. When an established network connection is migrated between listener sockets within the same SO_REUSEPORT group, applications waiting for new connections may not be properly notified. This can cause poll(), epoll_wait(), and blocking accept() calls to remain unresponsive indefinitely, leading to a Denial of Service (DoS) for affected applications.
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. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-2026-32396

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 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: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

What

In the Linux kernel, the following vulnerability has been resolved: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

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: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

Why

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

How

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

02

Exploit reality and attack path

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

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

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

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

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

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32396Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: tcp: call sk_data_ready() after listener migration When inet_csk_listen_stop() migrates an established child socket from a closing listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk) after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add() succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener. Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is visible via inet_ehash_insert(), the success path no longer touches nsk directly.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-45984 Référence CVE CVE-2026-45985 https://www.cve.org/CVERecord?id=CVE-2026-45985 Référence CVE CVE-2026-45986 https://www.cve.org/CVERecord?id=CVE-2026-45986 Référence CVE CVE-2026-45987 https://www.cve.org/CVERecord?id=CVE-2026-45987 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-46002 https://www.cve.org/CVERecord?id=CVE-2026-46002 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45985 Référence CVE CVE-2026-45986 https://www.cve.org/CVERecord?id=CVE-2026-45986 Référence CVE CVE-2026-45987 https://www.cve.org/CVERecord?id=CVE-2026-45987 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-46002 https://www.cve.org/CVERecord?id=CVE-2026-46002 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45873 Référence CVE CVE-2026-45904 https://www.cve.org/CVERecord?id=CVE-2026-45904 Référence CVE CVE-2026-45905 https://www.cve.org/CVERecord?id=CVE-2026-45905 Référence CVE CVE-2026-45913 https://www.cve.org/CVERecord?id=CVE-2026-45913 Référence CVE CVE-2026-45915 https://www.cve.org/CVERecord?id=CVE-2026-45915 Référence CVE CVE-2026-45917 https://www.cve.org/CVERecord?id=CVE-2026-45917 Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-45973 https://www.cve.org/CVERecord?id=CVE-2026-45973 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46026 https://www.cve.org/CVERecord?id=CVE-2026-46026 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=CVE-2026-46037 Référence CVE CVE-2026-46038 https://www.cve.org/CVERecord?id=CVE-2026-46038 Référence CVE CVE-2026-46080 https://www.cve.org/CVERecord?id=CVE-2026-46080 Référence CVE CVE-2026-46084 https://www.cve.org/CVERecord?id=CVE-2026-46084 Référence CVE CVE-2026-46109 https://www.cve.org/CVERecord?id=CVE-2026-46109 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=CVE-2026-46117 Référence CVE CVE-2026-46126 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46026 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45987 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-45996 https://www.cve.org/CVERecord?id=CVE-2026-45996 Référence CVE CVE-2026-46001 https://www.cve.org/CVERecord?id=CVE-2026-46001 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46026 https://www.cve.org/CVERecord?id=CVE-2026-46026 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46034 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45984 Référence CVE CVE-2026-45985 https://www.cve.org/CVERecord?id=CVE-2026-45985 Référence CVE CVE-2026-45986 https://www.cve.org/CVERecord?id=CVE-2026-45986 Référence CVE CVE-2026-45987 https://www.cve.org/CVERecord?id=CVE-2026-45987 Référence CVE CVE-2026-45994 https://www.cve.org/CVERecord?id=CVE-2026-45994 Référence CVE CVE-2026-46002 https://www.cve.org/CVERecord?id=CVE-2026-46002 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46037 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-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 https://www.cve.org/CVERecord?id=CVE-2026-46020 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 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-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 https://www.cve.org/CVERecord?id=CVE-2026-46020 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45996 Référence CVE CVE-2026-45997 https://www.cve.org/CVERecord?id=CVE-2026-45997 Référence CVE CVE-2026-45999 https://www.cve.org/CVERecord?id=CVE-2026-45999 Référence CVE CVE-2026-46002 https://www.cve.org/CVERecord?id=CVE-2026-46002 Référence CVE CVE-2026-46003 https://www.cve.org/CVERecord?id=CVE-2026-46003 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46005 https://www.cve.org/CVERecord?id=CVE-2026-46005 Référence CVE CVE-2026-46006 https://www.cve.org/CVERecord?id=CVE-2026-46006 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=CVE-2026-46024 Référence CVE CVE-2026-46026 https://www.cve.org/CVERecord?id=CVE-2026-46026 Référence CVE CVE-2026-46027 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 https://www.cve.org/CVERecord?id=CVE-2026-46020 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46006 Référence CVE CVE-2026-46007 https://www.cve.org/CVERecord?id=CVE-2026-46007 Référence CVE CVE-2026-46008 https://www.cve.org/CVERecord?id=CVE-2026-46008 Référence CVE CVE-2026-46009 https://www.cve.org/CVERecord?id=CVE-2026-46009 Référence CVE CVE-2026-46010 https://www.cve.org/CVERecord?id=CVE-2026-46010 Référence CVE CVE-2026-46011 https://www.cve.org/CVERecord?id=CVE-2026-46011 Référence CVE CVE-2026-46012 https://www.cve.org/CVERecord?id=CVE-2026-46012 Référence CVE CVE-2026-46013 https://www.cve.org/CVERecord?id=CVE-2026-46013 Référence CVE CVE-2026-46014 https://www.cve.org/CVERecord?id=CVE-2026-46014 Référence CVE CVE-2026-46015 https://www.cve.org/CVERecord?id=CVE-2026-46015 Référence CVE CVE-2026-46016 https://www.cve.org/CVERecord?id=CVE-2026-46016 Référence CVE CVE-2026-46018 https://www.cve.org/CVERecord?id=CVE-2026-46018 Référence CVE CVE-2026-46019 https://www.cve.org/CVERecord?id=CVE-2026-46019 Référence CVE CVE-2026-46020 https://www.cve.org/CVERecord?id=CVE-2026-46020 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46022 https://www.cve.org/CVERecord?id=CVE-2026-46022 Référence CVE CVE-2026-46023 https://www.cve.org/CVERecord?id=CVE-2026-46023 Référence CVE CVE-2026-46024 https://www.cve.org/CVERecord?id=

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

mai 2026 Bulletin de sécurité Microsoft CVE-2026-45999 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46000 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46002 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46003 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46004 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46005 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46006 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46009 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46011 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46012 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46015 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46016 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46018 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46019 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46021 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46022 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46023 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46024 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46026 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46027 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46031 du 28 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-020075LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。tcpのリスナー移行後にsk_data_ready()を呼び出すinet_csk_listen_stop()が、確立された子ソケットを終了中のリスナーから同じSO_REUSEPORTグループ内の別ソケットへ移行する際、対象リスナーはinet_csk_reqsk_queue_add()経由で新しいacceptキューエントリを取得しますが、その経路では対象リスナーの待機者に通知が一切行われません。ノンブロッキングのaccept()はキューを直接確認するため動作しますが、poll()/epoll_wait()の待機者やブロッキングaccept()の呼び出し元は無期限にスリープ状態のままになる可能性があります。inet_csk_listen_stop()内で移行が成功した後にREAD_ONCE(nsk-sk_data_ready)(nsk)を呼び出すようにしました。しかしながら、inet_csk_reqsk_queue_add()の成功後、reuseport_migrate_sock()で取得された参照は実質的にnreq-rsk_listenerに移行します。別のCPUがaccept()またはリスナーのシャットダウンを介してnreqをデキューし、reqsk_put()を実行してそのリスナー参照を解放する可能性があります。リスナーはSOCK_RCU_FREEであるため、queue_add()後のnskの参照解除はrcu_read_lock()/rcu_read_unlock()でラップし、その経路の既存sock_net(nsk)アクセスもカバーしています。reqsk_timer_handler()パスには以下の2つの理由で同様の変更は不要です。半開要求は最終ACK後にのみ読み取り可能となり、tcp_child_process()が既にリスナーを起こすこと、およびnreqがinet_ehash_insert()を通じて可視化された後、成功した経路はもはや直接nskに触れなくなることです。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.14, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 7.0.*, 7.1 ≤ *
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 27 May 2026 · Last source change 8 Sept 2026, 08:49 UTC · CWE not yet assigned

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; bpftool as a component of Red Hat Enterprise Linux 9; kernel as a component of Red Hat Enterprise Linux 9; kernel-64k as a component of Red Hat Enterprise Linux 9; kernel-64k-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-64k-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-modules as a component of Red Hat Enterprise Linux 9; and 92 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
    After
    kernel as a component of Red Hat Enterprise Linux 6; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6; kernel-bootwrapper as a component of Red Hat Enterprise Linux 6; kernel-debug as a component of Red Hat Enterprise Linux 6; kernel-debug-devel as a component of Red Hat Enterprise Linux 6; kernel-devel as a component of Red Hat Enterprise Linux 6; kernel-doc as a component of Red Hat Enterprise Linux 6; kernel-firmware as a component of Red Hat Enterprise Linux 6; kernel-headers as a component of Red Hat Enterprise Linux 6; kernel-kdump as a component of Red Hat Enterprise Linux 6; kernel-kdump-devel as a component of Red Hat Enterprise Linux 6; kernel.src as a component of Red Hat Enterprise Linux 6; perf as a component of Red Hat Enterprise Linux 6; python-perf as a component of Red Hat Enterprise Linux 6; 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; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; and 6 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.52.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    54b92e84193749c9968aff2dd46e3b0f42643e18 < 7aa7933a5607b1e5b56f322d17265c1d0ea02c51; 54b92e84193749c9968aff2dd46e3b0f42643e18 < 14e9bb6eba8f59dcc637702e4744ae5e30660d76; 54b92e84193749c9968aff2dd46e3b0f42643e18 < ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b; 54b92e84193749c9968aff2dd46e3b0f42643e18 < bebd058ef40c67a81fe6d9ee8beaa4ede90e0704; 54b92e84193749c9968aff2dd46e3b0f42643e18 < 83bb57635d7cbafde32f865b577ecfd969f02337; 54b92e84193749c9968aff2dd46e3b0f42643e18 < 12625b4da84caf4d84a04988710a7b9bcf702b18; 54b92e84193749c9968aff2dd46e3b0f42643e18 < 3864c6ba1e041bc75342353a70fa2a2c6f909923; 5.14 · Fixed: < 5.14; 5.15.209 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.86 ≤ 6.12.*; 6.18.27 ≤ 6.18.*; 7.0.4 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 54b92e84193749c9968aff2dd46e3b0f42643e18 < 7aa7933a5607b1e5b56f322d17265c1d0ea02c51, 54b92e84193749c9968aff2dd46e3b0f42643e18 < 14e9bb6eba8f59dcc637702e4744ae5e30660d76, 54b92e84193749c9968aff2dd46e3b0f42643e18 < ab5fdcd535645f6dbe6e9e21d96a08d141e88b4b, 54b92e84193749c9968aff2dd46e3b0f42643e18 < bebd058ef40c67a81fe6d9ee8beaa4ede90e0704, 54b92e84193749c9968aff2dd46e3b0f42643e18 < 83bb57635d7cbafde32f865b577ecfd969f02337, 54b92e84193749c9968aff2dd46e3b0f42643e18 < 12625b4da84caf4d84a04988710a7b9bcf702b18, 54b92e84193749c9968aff2dd46e3b0f42643e18 < 3864c6ba1e041bc75342353a70fa2a2c6f909923, 5.14 · Fixed: Linux: < 5.14, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-32396↗Vendor CSAF · SUSE Product Security Team↗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-46015 · cve.blacktree.nl