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

inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.45% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 13 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.

17 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 13 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 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-oracle-6.14Affected, 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
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-53175 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2026-53175
46 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-53175 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Linux kernel: Memory corruption via use-after-free in internet fragmentation
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's internet fragmentation code. This vulnerability, a use-after-free, occurs due to a timing issue during the shutdown of network namespaces. A local attacker could exploit this by manipulating network namespace operations, potentially leading to memory corruption. This could result in a system crash, causing a denial of service, or in some cases, allow for an increase in their access privileges.
Remediation
No remediation text is recorded.
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-39266

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 13 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: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.

What

In the Linux kernel, the following vulnerability has been resolved: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Expired Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-825 ↗

CWE-825: Expired Pointer Dereference. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-825
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-39266Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: inet: frags: fix use-after-free caused by the fqdir_pre_exit() flush On netns teardown, fqdir_pre_exit() walks the fqdir rhashtable and flushes every fragment queue that is not yet complete using inet_frag_queue_flush(). That helper frees all the skbs queued on the fragment queue but does not set INET_FRAG_COMPLETE, and leaves q->fragments_tail and q->last_run_head pointing at the freed skbs. The queue itself stays in the rhashtable. fqdir_pre_exit() first lowers high_thresh to 0 to stop new queue lookups, but it cannot stop a fragment that already obtained the queue through inet_frag_find() earlier and stalled just before taking the queue lock. Once that fragment resumes after the flush and takes the queue lock, it passes the INET_FRAG_COMPLETE check and then dereferences the freed fragments_tail. inet_frag_queue_insert() reads FRAG_CB() and ->len of that pointer and, on the append path, writes ->next_frag, causing a slab use-after-free. IPv6, nf_conntrack_reasm6 and 6lowpan reassembly share the same flush path and are affected as well. Reset rb_fragments, fragments_tail and last_run_head in inet_frag_queue_flush() so a flushed queue no longer points at the freed skbs. A fragment that resumes after the flush and takes the queue lock then finds an empty queue and starts a new run instead of dereferencing the freed fragments_tail. ip_frag_reinit() already performed this reset after its own flush, so drop the now duplicate code there.

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 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-53165 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53168 https://www.cve.org/CVERecord?id=CVE-2026-53168 Référence CVE CVE-2026-53169 https://www.cve.org/CVERecord?id=CVE-2026-53169 Référence CVE CVE-2026-53170 https://www.cve.org/CVERecord?id=CVE-2026-53170 Référence CVE CVE-2026-53171 https://www.cve.org/CVERecord?id=CVE-2026-53171 Référence CVE CVE-2026-53172 https://www.cve.org/CVERecord?id=CVE-2026-53172 Référence CVE CVE-2026-53173 https://www.cve.org/CVERecord?id=CVE-2026-53173 Référence CVE CVE-2026-53174 https://www.cve.org/CVERecord?id=CVE-2026-53174 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 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-53165 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53168 https://www.cve.org/CVERecord?id=CVE-2026-53168 Référence CVE CVE-2026-53169 https://www.cve.org/CVERecord?id=CVE-2026-53169 Référence CVE CVE-2026-53170 https://www.cve.org/CVERecord?id=CVE-2026-53170 Référence CVE CVE-2026-53171 https://www.cve.org/CVERecord?id=CVE-2026-53171 Référence CVE CVE-2026-53172 https://www.cve.org/CVERecord?id=CVE-2026-53172 Référence CVE CVE-2026-53173 https://www.cve.org/CVERecord?id=CVE-2026-53173 Référence CVE CVE-2026-53174 https://www.cve.org/CVERecord?id=CVE-2026-53174 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 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-53165 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 Référence CVE CVE-2026-53168 https://www.cve.org/CVERecord?id=CVE-2026-53168 Référence CVE CVE-2026-53169 https://www.cve.org/CVERecord?id=CVE-2026-53169 Référence CVE CVE-2026-53170 https://www.cve.org/CVERecord?id=CVE-2026-53170 Référence CVE CVE-2026-53171 https://www.cve.org/CVERecord?id=CVE-2026-53171 Référence CVE CVE-2026-53172 https://www.cve.org/CVERecord?id=CVE-2026-53172 Référence CVE CVE-2026-53173 https://www.cve.org/CVERecord?id=CVE-2026-53173 Référence CVE CVE-2026-53174 https://www.cve.org/CVERecord?id=CVE-2026-53174 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53178 https://www.cve.org/CVERecord?id=CVE-2026-53178 Référence CVE CVE-2026-53179 https://www.cve.org/CVERecord?id=CVE-2026-53179 Référence CVE CVE-2026-53180 https://www.cve.org/CVERecord?id=CVE-2026-53180 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 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-53088 Référence CVE CVE-2026-53106 https://www.cve.org/CVERecord?id=CVE-2026-53106 Référence CVE CVE-2026-53107 https://www.cve.org/CVERecord?id=CVE-2026-53107 Référence CVE CVE-2026-53123 https://www.cve.org/CVERecord?id=CVE-2026-53123 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=CVE-2026-53129 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53132 https://www.cve.org/CVERecord?id=CVE-2026-53132 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53134 https://www.cve.org/CVERecord?id=CVE-2026-53134 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53212 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-53125 Référence CVE CVE-2026-53126 https://www.cve.org/CVERecord?id=CVE-2026-53126 Référence CVE CVE-2026-53127 https://www.cve.org/CVERecord?id=CVE-2026-53127 Référence CVE CVE-2026-53128 https://www.cve.org/CVERecord?id=CVE-2026-53128 Référence CVE CVE-2026-53129 https://www.cve.org/CVERecord?id=CVE-2026-53129 Référence CVE CVE-2026-53130 https://www.cve.org/CVERecord?id=CVE-2026-53130 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53151 https://www.cve.org/CVERecord?id=CVE-2026-53151 Référence CVE CVE-2026-53174 https://www.cve.org/CVERecord?id=CVE-2026-53174 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53148 Référence CVE CVE-2026-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53150 https://www.cve.org/CVERecord?id=CVE-2026-53150 Référence CVE CVE-2026-53152 https://www.cve.org/CVERecord?id=CVE-2026-53152 Référence CVE CVE-2026-53157 https://www.cve.org/CVERecord?id=CVE-2026-53157 Référence CVE CVE-2026-53158 https://www.cve.org/CVERecord?id=CVE-2026-53158 Référence CVE CVE-2026-53159 https://www.cve.org/CVERecord?id=CVE-2026-53159 Référence CVE CVE-2026-53160 https://www.cve.org/CVERecord?id=CVE-2026-53160 Référence CVE CVE-2026-53161 https://www.cve.org/CVERecord?id=CVE-2026-53161 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53177 https://www.cve.org/CVERecord?id=CVE-2026-53177 Référence CVE CVE-2026-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53182 https://www.cve.org/CVERecord?id=CVE-2026-53182 Référence CVE CVE-2026-53183 https://www.cve.org/CVERecord?id=CVE-2026-53183 Référence CVE CVE-2026-53184 https://www.cve.org/CVERecord?id=CVE-2026-53184 Référence CVE CVE-2026-53185 https://www.cve.org/CVERecord?id=CVE-2026-53185 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53189 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-53086 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53131 https://www.cve.org/CVERecord?id=CVE-2026-53131 Référence CVE CVE-2026-53146 https://www.cve.org/CVERecord?id=CVE-2026-53146 Référence CVE CVE-2026-53147 https://www.cve.org/CVERecord?id=CVE-2026-53147 Référence CVE CVE-2026-53148 https://www.cve.org/CVERecord?id=CVE-2026-53148 Référence CVE CVE-2026-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53150 https://www.cve.org/CVERecord?id=CVE-2026-53150 Référence CVE CVE-2026-53151 https://www.cve.org/CVERecord?id=CVE-2026-53151 Référence CVE CVE-2026-53175 https://www.cve.org/CVERecord?id=CVE-2026-53175 Référence CVE CVE-2026-53176 https://www.cve.org/CVERecord?id=CVE-2026-53176 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=CVE-2026-53186 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53215 https://www.cve.org/CVERecord?id=CVE-2026-53215 Référence CVE CVE-2026-53216 https://www.cve.org/CVERecord?id=CVE-2026-53216 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました:inet: frags: fqdir_pre_exit() のフラッシュに起因する use-after-free（解放後使用）を修正ネットワーク名前空間（netns）の解体時、fqdir_pre_exit() は fqdir の rhashtable を走査し、inet_frag_queue_flush() を用いて未完了のすべてのフラグメントキューをフラッシュします。このヘルパーは、フラグメントキューにキューイングされたすべての skb を解放しますが、INET_FRAG_COMPLETE を設定せず、q->fragments_tail および q->last_run_head が解放済みの skb を指したままにします。キュー自体は rhashtable 内に残ります。fqdir_pre_exit() はまず high_thresh を 0 に下げて新たなキュー探索を止めますが、すでに inet_frag_find() でキューを取得し、キューロックを取る直前で停止していたフラグメントを止めることはできません。フラッシュ後にそのフラグメントが再開してキューロックを取得すると、INET_FRAG_COMPLETE のチェックを通過し、その後、解放済みの fragments_tail を逆参照してしまいます。inet_frag_queue_insert() はそのポインタの FRAG_CB() と ->len を読み取り、追記パスでは ->next_frag に書き込みを行うため、slab の use-after-free を引き起こします。IPv6、nf_conntrack_reasm6、6lowpan の再組立も同じフラッシュ経路を共有しており、同様に影響を受けます。inet_frag_queue_flush() 内で rb_fragments、fragments_tail、last_run_head をリセットし、フラッシュされたキューが解放済みの skb を指さないようにします。フラッシュ後に再開してキューロックを取得したフラグメントは、解放済みの fragments_tail を逆参照するのではなく、空のキューを見つけて新しい run を開始します。ip_frag_reinit() は独自のフラッシュ後にすでにこのリセットを実施していたため、そこにあった重複コードは削除します。

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.19, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 1 Sept 2026, 12:04 UTC · CWE-825 · Expired Pointer Dereference

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-39266
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. Affected versionsThe structured affected or fixed version information changed.
    Before
    22ee4010866da81aeee08e1ea3fddbe418feb212 < 0e823ca0e7391630784ae7dd0981b7ad170a93d9; 543555954b1ee8d1903a7020324efb41b0c97428 < c22599cc90e1cd5f8129c8670bd68a02ff7177b4; c70df25214ac9b32b53e18e6ae3b8f073ffa6903 < 89b909e9704587bfecc1aab1d37e98faee03b9f9; 006a5035b495dec008805df249f92c22c89c3d2e < 010c3313a4d178dc2d3ce958d2e5cb055e2864c1; 006a5035b495dec008805df249f92c22c89c3d2e < 32594b09854970d7ba83eb2dc8c69a2edd158c8e; 6.12.93 < 6.12.94; 6.18.3 < 6.18.36; 6.19 · Fixed: < 6.19; 6.12.94 ≤ 6.12.*; 6.18.36 ≤ 6.18.*; 7.0.13 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 22ee4010866da81aeee08e1ea3fddbe418feb212 < 0e823ca0e7391630784ae7dd0981b7ad170a93d9, 543555954b1ee8d1903a7020324efb41b0c97428 < c22599cc90e1cd5f8129c8670bd68a02ff7177b4, c70df25214ac9b32b53e18e6ae3b8f073ffa6903 < 89b909e9704587bfecc1aab1d37e98faee03b9f9, 006a5035b495dec008805df249f92c22c89c3d2e < 010c3313a4d178dc2d3ce958d2e5cb055e2864c1, 006a5035b495dec008805df249f92c22c89c3d2e < 32594b09854970d7ba83eb2dc8c69a2edd158c8e, 6.12.93 < 6.12.94, 6.18.3 < 6.18.36, 6.19 · Fixed: Linux: < 6.19, 6.12.94 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-39266↗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-53175 · cve.blacktree.nl