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

eventpoll: fix ep_remove struct eventpoll / struct file UAF

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 3 Oct 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 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.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-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.

2 current
CVE-2026-46242 · CSAF 2.0 · revision 26 · interimSUSE Product Security TeamCVE-2026-46242
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-46242 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: eventpoll: fix ep_remove struct eventpoll / struct file UAF
1 known affected

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

  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in the Linux kernel's `eventpoll` mechanism. A Use-After-Free (UAF) vulnerability, where the system attempts to access memory after it has been freed, can occur during the removal of a file. A local attacker could exploit this race condition to corrupt memory, potentially leading to privilege escalation or arbitrary code execution. This allows an attacker to gain elevated control over the system.
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-33459

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

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: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

What

In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-33459Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file UAF ep_remove() (via ep_remove_file()) cleared file->f_ep under file->f_lock but then kept using @file inside the critical section (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock). A concurrent __fput() taking the eventpoll_release() fastpath in that window observed the transient NULL, skipped eventpoll_release_file() and ran to f_op->release / file_free(). For the epoll-watches-epoll case, f_op->release is ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which kfree()s the watched struct eventpoll. Its embedded ->refs hlist_head is exactly where epi->fllink.pprev points, so the subsequent hlist_del_rcu()'s "*pprev = next" scribbles into freed kmalloc-192 memory. In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot backing @file could be recycled by alloc_empty_file() -- reinitializing f_lock and f_ep -- while ep_remove() is still nominally inside that lock. The upshot is an attacker-controllable kmem_cache_free() against the wrong slab cache. Pin @file via epi_fget() at the top of ep_remove() and gate the critical section on the pin succeeding. With the pin held @file cannot reach refcount zero, which holds __fput() off and transitively keeps the watched struct eventpoll alive across the hlist_del_rcu() and the f_lock use, closing both UAFs. If the pin fails @file has already reached refcount zero and its __fput() is in flight. Because we bailed before clearing f_ep, that path takes the eventpoll_release() slow path into eventpoll_release_file() and blocks on ep->mtx until the waiter side's ep_clear_and_put() drops it. The bailed epi's share of ep->refcount stays intact, so the trailing ep_refcount_dec_and_test() in ep_clear_and_put() cannot free the eventpoll out from under eventpoll_release_file(); the orphaned epi is then cleaned up there. A successful pin also proves we are not racing eventpoll_release_file() on this epi, so drop the now-redundant re-check of epi->dying under f_lock. The cheap lockless READ_ONCE(epi->dying) fast-path bailout stays.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-2026-1756Linux Kernel: Schwachstelle ermöglicht Privilegieneskalation und Denial of Service

Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel für eine Privilegieneskalation ausnutzen, sowie um einen Denial of Service Zustand oder andere, nicht spezifizierte Auswirkungen herbeizuführen.

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-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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 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-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 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-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43493 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45919 https://www.cve.org/CVERecord?id=CVE-2026-45919 Référence CVE CVE-2026-45942 https://www.cve.org/CVERecord?id=CVE-2026-45942 Référence CVE CVE-2026-46076 https://www.cve.org/CVERecord?id=CVE-2026-46076 Référence CVE CVE-2026-46199 https://www.cve.org/CVERecord?id=CVE-2026-46199 Référence CVE CVE-2026-46204 https://www.cve.org/CVERecord?id=CVE-2026-46204 Référence CVE CVE-2026-46230 https://www.cve.org/CVERecord?id=CVE-2026-46230 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=CVE-2026-46317 Référence CVE CVE-2026-46325 https://www.cve.org/CVERecord?id=CVE-2026-46325 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53059 https://www.cve.org/CVERecord?id=CVE-2026-53059 Référence CVE CVE-2026-53071 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-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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 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-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 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-46267 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46070 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46150 https://www.cve.org/CVERecord?id=CVE-2026-46150 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 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-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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 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-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 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-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45968 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=CVE-2026-46037 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46078 https://www.cve.org/CVERecord?id=CVE-2026-46078 Référence CVE CVE-2026-46091 https://www.cve.org/CVERecord?id=CVE-2026-46091 Référence CVE CVE-2026-46107 https://www.cve.org/CVERecord?id=CVE-2026-46107 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46127 https://www.cve.org/CVERecord?id=CVE-2026-46127 Référence CVE CVE-2026-46195 https://www.cve.org/CVERecord?id=CVE-2026-46195 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52920 https://www.cve.org/CVERecord?id=CVE-2026-52920 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52925 https://www.cve.org/CVERecord?id=CVE-2026-52925 Référence CVE CVE-2026-52929 https://www.cve.org/CVERecord?id=CVE-2026-52929 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23240 Référence CVE CVE-2026-23449 https://www.cve.org/CVERecord?id=CVE-2026-23449 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-46037 https://www.cve.org/CVERecord?id=CVE-2026-46037 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53205 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-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=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 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-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 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-46147 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46168 https://www.cve.org/CVERecord?id=CVE-2026-46168 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46174 https://www.cve.org/CVERecord?id=CVE-2026-46174 Référence CVE CVE-2026-46180 https://www.cve.org/CVERecord?id=CVE-2026-46180 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46193 https://www.cve.org/CVERecord?id=CVE-2026-46193 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 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-46245 https://www.cve.org/CVERecord?id=CVE-2026-46245 Référence CVE CVE-2026-46265 https://www.cve.org/CVERecord?id=CVE-2026-46265 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46306 https://www.cve.org/CVERecord?id=CVE-2026-46306 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46323 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-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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 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=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-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46282 https://www.cve.org/CVERecord?id=CVE-2026-46282 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43465 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 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-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46325 https://www.cve.org/CVERecord?id=CVE-2026-46325 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52955 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-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=CVE-2026-46289 Référence CVE CVE-2026-46291 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-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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 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-46246 https://www.cve.org/CVERecord?id=CVE-2026-46246 Référence CVE CVE-2026-46247 https://www.cve.org/CVERecord?id=CVE-2026-46247 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=CVE-2026-46250 Référence CVE CVE-2026-46251 https://www.cve.org/CVERecord?id=CVE-2026-46251 Référence CVE CVE-2026-46253 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-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=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-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-46247 https://www.cve.org/CVERecord?id=CVE-2026-46247 Référence CVE CVE-2026-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46252 https://www.cve.org/CVERecord?id=CVE-2026-46252 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=

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

d?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=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-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 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-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 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-46267 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45984 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 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-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-46173 https://www.cve.org/CVERecord?id=CVE-2026-46173 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-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53166 https://www.cve.org/CVERecord?id=CVE-2026-53166 Référence CVE CVE-2026-53266 https://www.cve.org/CVERecord?id=CVE-2026-53266 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Gestion détaillée du document le 17 juillet 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.gou

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

d?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=CVE-2026-46242 Référence CVE CVE-2026-46252 https://www.cve.org/CVERecord?id=CVE-2026-46252 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 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-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=CVE-2026-46331 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=C

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。eventpollのep_removeにおけるstruct eventpollおよびstruct fileのUse-After-Free（UAF）問題に対する修正です。ep_remove()（ep_remove_file()経由）ではfile-f_lockの下でfile-f_epをクリアしましたが、その後もクリティカルセクション内で@fileを使用し続けていました（is_file_epoll()やhlist_del_rcu()をhead経由で呼び出し、spin_unlockを行っていました）。同時に動作していた__fput()はeventpoll_release()の高速パスを経由し、その過程で一時的にNULLとなったfile-f_epを観察し、eventpoll_release_file()をスキップしてf_op-releaseおよびfile_free()を実行していました。epoll-watches-epollのケースでは、f_op-releaseはep_eventpoll_release() - ep_clear_and_put() - ep_free()となり、これが監視中のstruct eventpollをkfree()します。この中の埋め込みメンバのrefsにあるhlist_headはepi-fllink.pprevが指している場所と同一であり、その後のhlist_del_rcu()の「*pprev = next」により、解放済みのkmalloc-192メモリが上書きされる問題がありました。さらにstruct fileはSLAB_TYPESAFE_BY_RCUであるため、ep_remove()がまだそのロック内にいる間に、@fileを裏付けるスロットがalloc_empty_file()により再利用され、f_lockとf_epが再初期化される可能性があります。つまり、攻撃者が制御可能なkmem_cache_free()が誤ったスラブキャッシュに対して実行される事態が発生する恐れがありました。修正では、ep_remove()の先頭でepi_fget()により@fileをピン留めし、ピン留めが成功した場合にのみクリティカルセクションに入るようにしました。ピン留めした状態の@fileは参照カウントがゼロにならず、__fput()の実行を抑制します。これにより、監視されているstruct eventpollがhlist_del_rcu()およびf_lockの使用を跨いで有効な状態に保たれ、両方のUse-After-Freeを防止します。もしピン留めが失敗した場合は、@fileはすでに参照カウントゼロに達しており、__fput()が進行中です。f_epをクリアする前に早期リターンしているため、その経路はeventpoll_release()のスローパスであるeventpoll_release_file()を通り、ep-mtx上で待機し、待機側のep_clear_and_put()がロックを解放するのを待ちます。早期リターンしたepiのep-refcountのシェアは維持されているため、ep_clear_and_put()の最後のep_refcount_dec_and_test()はeventpoll_release_file()の動作中にeventpollを強制解放しません。孤立したepiはそこで適切にクリーンアップされます。ピン留め成功はまた、このepiに対してeventpoll_release_file()と競合していないことも証明するため、f_lock下のepi-dyingを再チェックしていた冗長な処理を削除しました。安価なロックなしのREAD_ONCE(epi-dying)による高速パスでの早期リターンはそのまま残します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6873Linux 제품 보안 업데이트 권고

Linux Kernel에서 발생하는 Use After Free 취약점(CVE-2026-46242) [1][2]

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: < 6.4, 5.15.222 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 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 30 May 2026 · Last source change 3 Oct 2026, 10:55 UTC · CWE-416 · Use After Free

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    a1f93804449d13f97dabd4b996817de4bf1ed67a < 3e1144d2515d28e4312e663ea05eac203101491d; 58c9b016e12855286370dfb704c08498edbc857a < 2de4db145b2992da496fea6c51f9839be678ae24; 58c9b016e12855286370dfb704c08498edbc857a < 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5; 58c9b016e12855286370dfb704c08498edbc857a < ef4ca02e95363e78977ca04340d44fe3b4b2b81f; 58c9b016e12855286370dfb704c08498edbc857a < ced39b6a8062bac5c18a1c3df85634107eb8664a; 58c9b016e12855286370dfb704c08498edbc857a < a6dc643c69311677c574a0f17a3f4d66a5f3744b; f2451def095c1743adcfcb0cb5dadc86034e162a; 6.1.175 < 6.1.178 · Fixed: < 6.4; 6.1.178 ≤ 6.1.*; 6.6.144 ≤ 6.6.*; 6.12.95 ≤ 6.12.*; 6.18.33 ≤ 6.18.*; 7.0.10 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: f2451def095c1743adcfcb0cb5dadc86034e162a < a10fbbe74e1c743beb1bb312109366667461df8a, a1f93804449d13f97dabd4b996817de4bf1ed67a < 3e1144d2515d28e4312e663ea05eac203101491d, 58c9b016e12855286370dfb704c08498edbc857a < 2de4db145b2992da496fea6c51f9839be678ae24, 58c9b016e12855286370dfb704c08498edbc857a < 9324de74a3a59b9fde9b62ee45ebaa71458ba2e5, 58c9b016e12855286370dfb704c08498edbc857a < ef4ca02e95363e78977ca04340d44fe3b4b2b81f, 58c9b016e12855286370dfb704c08498edbc857a < ced39b6a8062bac5c18a1c3df85634107eb8664a, 58c9b016e12855286370dfb704c08498edbc857a < a6dc643c69311677c574a0f17a3f4d66a5f3744b, 5.15.209 < 5.15.222, 6.1.175 < 6.1.178, 6.4 · Fixed: Linux: < 6.4, 5.15.222 ≤ 5.15.*, 6.1.178 ≤ 6.1.*, 6.6.144 ≤ 6.6.*, 6.12.95 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-common-aarch64-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-doc-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1573 more
    After
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-259.26.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-devel-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-devel-matched-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-devel-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-devel-matched-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-259.26.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1626 more
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-common-aarch64-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-doc-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1573 more
    After
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-common-aarch64-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-doc-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1573 more
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-common-aarch64-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-doc-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1573 more
    After
    Fixed: kernel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-0:6.12.0-231.15.el10nv.src as a component of NVIDIA for RHEL 10; kernel-64k-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-64k-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-abi-stablelists-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-core-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debug-modules-extra-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-debuginfo-common-aarch64-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-devel-matched-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; kernel-doc-0:6.12.0-231.15.el10nv.noarch as a component of NVIDIA for RHEL 10; kernel-modules-0:6.12.0-231.15.el10nv.aarch64 as a component of NVIDIA for RHEL 10; and 1573 more
    Red Hat Product Security ↗
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-33459↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46242 · cve.blacktree.nl