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

sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 25 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

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

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-46227 · CSAF 2.0 · revision 36 · interimSUSE Product Security TeamCVE-2026-46227
67 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-46227 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL
2,168 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-64k-debug-debuginfo-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debug-devel-matched-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-debuginfo-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-64k-devel-matched-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.82.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.82.1.el10_0.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-debuginfo-0:6.12.0-55.82.1.el10_0.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.82.1.el10_0.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
  • kernel-debug-devel-0:6.12.0-55.82.1.el10_0.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v. 10.0)
Summary
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A race condition exists in the `SCTP_SENDALL` path where a cached list entry is not properly revalidated after the socket lock is temporarily released. This allows a local attacker or a remote attacker (via a network abort) to trigger a use-after-free or type confusion vulnerability. Successful exploitation can lead to a controlled indirect call, potentially resulting in arbitrary code execution.
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-2026-32854

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

What

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

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: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

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 → Time-of-check Time-of-use (TOCTOU) Race Condition → 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: a standard category for the underlying weakness.
CWE-367 ↗

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

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.
CWE-367
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-32854Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL The SCTP_SENDALL path in sctp_sendmsg() iterates ep->asocs with list_for_each_entry_safe(), which caches the next entry in @tmp before the loop body runs. The body calls sctp_sendmsg_to_asoc(), which may drop the socket lock inside sctp_wait_for_sndbuf(). While the lock is dropped, another thread can SCTP_SOCKOPT_PEELOFF the association cached in @tmp, migrating it to a new endpoint via sctp_sock_migrate() (list_del_init() + list_add_tail() to newep->asocs), and optionally close the new socket which frees the association via kfree_rcu(). The cached @tmp can also be freed by a network ABORT for that association, processed in softirq while the lock is dropped. sctp_wait_for_sndbuf() revalidates @asoc (the current entry) on re-lock via the "sk != asoc->base.sk" and "asoc->base.dead" checks, but nothing revalidates @tmp. After a successful return, the iterator advances to the stale @tmp, yielding either a use-after-free (if the peeled socket was closed) or a list-walk onto the new endpoint's list head (type confusion of &newep->asocs as a struct sctp_association *). Both are reachable from CapEff=0; the type-confusion path gives controlled indirect call via the outqueue.sched->init_sid pointer. Fix by re-deriving @tmp from @asoc after sctp_sendmsg_to_asoc() returns. @asoc is known to still be on ep->asocs at that point: the only callers that list_del an association from ep->asocs are sctp_association_free() (which sets asoc->base.dead) and sctp_assoc_migrate() (which changes asoc->base.sk), and sctp_wait_for_sndbuf() checks both under the lock before any successful return; a tripped check propagates as err < 0 and the loop bails before the re-derive. The SCTP_ABORT path in sctp_sendmsg_check_sflags() returns 0 and the loop hits 'continue' before sctp_sendmsg_to_asoc() is ever called, so the @tmp cached by list_for_each_entry_safe() still covers the lock-held free that ba59fb027307 ("sctp: walk the list of asoc safely") was added for.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3043IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Official advisory ↗
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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46090 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46117 https://www.cve.org/CVERecord?id=CVE-2026-46117 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46145 https://www.cve.org/CVERecord?id=CVE-2026-46145 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46605 https://www.cve.org/CVERecord?id=CVE-2026-46605 Référence CVE CVE-2026-46625 https://www.cve.org/CVERecord?id=CVE-2026-46625 Référence CVE CVE-2026-46917 https://www.cve.org/CVERecord?id=CVE-2026-46917 Référence CVE CVE-2026-46968 https://www.cve.org/CVERecord?id=CVE-2026-46968 Référence CVE CVE-2026-47010 https://www.cve.org/CVERecord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 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-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46212 https://www.cve.org/CVERecord?id=CVE-2026-46212 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46236 https://www.cve.org/CVERecord?id=CVE-2026-46236 Référence CVE CVE-2026-46238 https://www.cve.org/CVERecord?id=CVE-2026-46238 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46249 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-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 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-46197 Référence CVE CVE-2026-46198 https://www.cve.org/CVERecord?id=CVE-2026-46198 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46212 https://www.cve.org/CVERecord?id=CVE-2026-46212 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46236 https://www.cve.org/CVERecord?id=CVE-2026-46236 Référence CVE CVE-2026-46238 https://www.cve.org/CVERecord?id=CVE-2026-46238 Référence CVE CVE-2026-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46150 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46161 https://www.cve.org/CVERecord?id=CVE-2026-46161 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46178 https://www.cve.org/CVERecord?id=CVE-2026-46178 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46289 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-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46207 Référence CVE CVE-2026-46211 https://www.cve.org/CVERecord?id=CVE-2026-46211 Référence CVE CVE-2026-46212 https://www.cve.org/CVERecord?id=CVE-2026-46212 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46216 https://www.cve.org/CVERecord?id=CVE-2026-46216 Référence CVE CVE-2026-46218 https://www.cve.org/CVERecord?id=CVE-2026-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=CVE-2026-46235 Référence CVE CVE-2026-46236 https://www.cve.org/CVERecord?id=CVE-2026-46236 Référence CVE CVE-2026-46238 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-46218 Référence CVE CVE-2026-46219 https://www.cve.org/CVERecord?id=CVE-2026-46219 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46221 https://www.cve.org/CVERecord?id=CVE-2026-46221 Référence CVE CVE-2026-46222 https://www.cve.org/CVERecord?id=CVE-2026-46222 Référence CVE CVE-2026-46223 https://www.cve.org/CVERecord?id=CVE-2026-46223 Référence CVE CVE-2026-46224 https://www.cve.org/CVERecord?id=CVE-2026-46224 Référence CVE CVE-2026-46225 https://www.cve.org/CVERecord?id=CVE-2026-46225 Référence CVE CVE-2026-46226 https://www.cve.org/CVERecord?id=CVE-2026-46226 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46228 https://www.cve.org/CVERecord?id=CVE-2026-46228 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46232 https://www.cve.org/CVERecord?id=CVE-2026-46232 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46069 Référence CVE CVE-2026-46082 https://www.cve.org/CVERecord?id=CVE-2026-46082 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-46124 https://www.cve.org/CVERecord?id=CVE-2026-46124 Référence CVE CVE-2026-46133 https://www.cve.org/CVERecord?id=CVE-2026-46133 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46185 https://www.cve.org/CVERecord?id=CVE-2026-46185 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 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-46199 Référence CVE CVE-2026-46205 https://www.cve.org/CVERecord?id=CVE-2026-46205 Référence CVE CVE-2026-46206 https://www.cve.org/CVERecord?id=CVE-2026-46206 Référence CVE CVE-2026-46208 https://www.cve.org/CVERecord?id=CVE-2026-46208 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46212 https://www.cve.org/CVERecord?id=CVE-2026-46212 Référence CVE CVE-2026-46214 https://www.cve.org/CVERecord?id=CVE-2026-46214 Référence CVE CVE-2026-46218 https://www.cve.org/CVERecord?id=CVE-2026-46218 Référence CVE CVE-2026-46220 https://www.cve.org/CVERecord?id=CVE-2026-46220 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46231 https://www.cve.org/CVERecord?id=CVE-2026-46231 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=CVE-2026-46235 Référence CVE CVE-2026-46236 https://www.cve.org/CVERecord?id=CVE-2026-46236 Référence CVE CVE-2026-46238 https://www.cve.org/CVERecord?id=CVE-2026-46238 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46155 https://www.cve.org/CVERecord?id=CVE-2026-46155 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46157 Référence CVE CVE-2026-46159 https://www.cve.org/CVERecord?id=CVE-2026-46159 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46162 https://www.cve.org/CVERecord?id=CVE-2026-46162 Référence CVE CVE-2026-46172 https://www.cve.org/CVERecord?id=CVE-2026-46172 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Gestion détaillée du document le 03 juillet 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales

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

d?id=CVE-2026-45852 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Gestion détaillée du document le 03 juillet 2026 Version initial

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

d?id=CVE-2026-46120 Référence CVE CVE-2026-46123 https://www.cve.org/CVERecord?id=CVE-2026-46123 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46157 https://www.cve.org/CVERecord?id=CVE-2026-46157 Référence CVE CVE-2026-46159 https://www.cve.org/CVERecord?id=CVE-2026-46159 Référence CVE CVE-2026-46176 https://www.cve.org/CVERecord?id=CVE-2026-46176 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Gestion détaillée du document le 26 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

d?id=CVE-2026-43116 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Gestion détaillée du document le 19 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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-46206 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46208 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46209 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46212 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46214 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46218 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46219 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46220 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46225 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46226 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46227 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46229 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46230 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46231 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46233 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46234 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46236 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46238 du 29 mai 2026 Bulletin de sécurité Microsoft CVE-2025-15649 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-42789 du 31 mai 2026 Bulletin de sécurité Microsoft CVE-2026-42790 du 31 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-019285LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。sctp: SCTP_SENDALL内のsctp_sendmsg_to_asoc()呼び出し後にリストカーソルを再検証します。sctp_sendmsg()のSCTP_SENDALLパスは、list_for_each_entry_safe()でep-asocsを反復処理し、ループ内でsctp_sendmsg_to_asoc()を呼び出します。この関数はsctp_wait_for_sndbuf()内でソケットロックを一時的に解放する可能性があります。ロックが解放されている間に、別のスレッドが関連付けを移動または解放することがあり、その結果ループのイテレータが解放済みのデータを参照し、use-after-freeや型混同が発生します。この問題により、型混同を起因とした制御可能な間接呼び出しが引き起こされる可能性があります。修正はsctp_sendmsg_to_asoc()の戻り後にイテレータを再取得し、関連付けの存在を再検証することで行いました。これにより、セキュリティ上の問題を防止します。

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: < 4.17, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.90 ≤ 6.12.*, 6.18.32 ≤ 6.18.*, 7.0.9 ≤ 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 28 May 2026 · Last source change 25 Aug 2026, 12:05 UTC · CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

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-32854
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceOther authority
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:59142; removed vendor advisory: access.redhat.com/RHSA-2026:59143; 5 further removals.
    Before
    patch: git.kernel.org/0c7b55974f97b78d1109025eadf084e74cbf330f · patch: git.kernel.org/0dbc8cde64280fc37cdd678cced34eaf96cfb197 · patch: git.kernel.org/1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078 · 13 more references
    After
    patch: git.kernel.org/0c7b55974f97b78d1109025eadf084e74cbf330f · patch: git.kernel.org/0dbc8cde64280fc37cdd678cced34eaf96cfb197 · patch: git.kernel.org/1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078 · 6 more references
    git.kernel.org ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:59142; added vendor advisory: access.redhat.com/RHSA-2026:59143; 5 further additions.
    Before
    patch: git.kernel.org/0c7b55974f97b78d1109025eadf084e74cbf330f · patch: git.kernel.org/0dbc8cde64280fc37cdd678cced34eaf96cfb197 · patch: git.kernel.org/1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078 · 6 more references
    After
    patch: git.kernel.org/0c7b55974f97b78d1109025eadf084e74cbf330f · patch: git.kernel.org/0dbc8cde64280fc37cdd678cced34eaf96cfb197 · patch: git.kernel.org/1bfb06ecb00f7fdf35dba8e8f2877346cbe5e078 · 13 more references
    git.kernel.org ↗
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-32854↗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-46227 · cve.blacktree.nl