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

netfilter: nft_fib: fix stale stack leak via the OIFNAME register

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% 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: No default targetRemediation target: Normal maintenance

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.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 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-53134 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-53134
295 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2026-39339

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.

What

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 → Missing Release of Memory after Effective Lifetime → 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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-401
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-39339Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_fib: fix stale stack leak via the OIFNAME register For NFT_FIB_RESULT_OIFNAME the destination register is declared with len = IFNAMSIZ (four 32-bit registers), but on the lookup-fail, RTN_LOCAL and oif-mismatch paths nft_fib{4,6}_eval() only writes one register via "*dest = 0". The remaining three registers are left as whatever was on the stack in nft_do_chain()'s struct nft_regs, and a downstream expression that loads the register span can leak that uninitialised kernel stack to userspace. The NFTA_FIB_F_PRESENT existence check has the same shape: it is only meaningful for NFT_FIB_RESULT_OIF, yet it was accepted for any result type while the eval stores a single byte via nft_reg_store8(), leaving the rest of the declared span stale. Fix both: - replace the bare "*dest = 0" in the eval with nft_fib_store_result(), which strscpy_pad()s the whole IFNAMSIZ for OIFNAME (and is already used on the other early-return path), and - restrict NFTA_FIB_F_PRESENT to NFT_FIB_RESULT_OIF and declare its destination as a single u8, so the marked span matches the one byte the eval writes.

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-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-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-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53140 https://www.cve.org/CVERecord?id=CVE-2026-53140 Référence CVE CVE-2026-53141 https://www.cve.org/CVERecord?id=CVE-2026-53141 Référence CVE CVE-2026-53142 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-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-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-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53140 https://www.cve.org/CVERecord?id=CVE-2026-53140 Référence CVE CVE-2026-53141 https://www.cve.org/CVERecord?id=CVE-2026-53141 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53090 Référence CVE CVE-2026-53091 https://www.cve.org/CVERecord?id=CVE-2026-53091 Référence CVE CVE-2026-53109 https://www.cve.org/CVERecord?id=CVE-2026-53109 Référence CVE CVE-2026-53118 https://www.cve.org/CVERecord?id=CVE-2026-53118 Référence CVE CVE-2026-53120 https://www.cve.org/CVERecord?id=CVE-2026-53120 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-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53140 https://www.cve.org/CVERecord?id=CVE-2026-53140 Référence CVE CVE-2026-53141 https://www.cve.org/CVERecord?id=CVE-2026-53141 Référence CVE CVE-2026-53142 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-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-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-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53140 https://www.cve.org/CVERecord?id=CVE-2026-53140 Référence CVE CVE-2026-53141 https://www.cve.org/CVERecord?id=CVE-2026-53141 Référence CVE CVE-2026-53142 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-53083 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2026-53105 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-53112 https://www.cve.org/CVERecord?id=CVE-2026-53112 Référence CVE CVE-2026-53113 https://www.cve.org/CVERecord?id=CVE-2026-53113 Référence CVE CVE-2026-53121 https://www.cve.org/CVERecord?id=CVE-2026-53121 Référence CVE CVE-2026-53123 https://www.cve.org/CVERecord?id=CVE-2026-53123 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-53134 https://www.cve.org/CVERecord?id=CVE-2026-53134 Référence CVE CVE-2026-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53138 https://www.cve.org/CVERecord?id=CVE-2026-53138 Référence CVE CVE-2026-53140 https://www.cve.org/CVERecord?id=CVE-2026-53140 Référence CVE CVE-2026-53143 https://www.cve.org/CVERecord?id=CVE-2026-53143 Référence CVE CVE-2026-53144 https://www.cve.org/CVERecord?id=CVE-2026-53144 Référence CVE CVE-2026-53146 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53060 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53107 https://www.cve.org/CVERecord?id=CVE-2026-53107 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-53134 https://www.cve.org/CVERecord?id=CVE-2026-53134 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-53149 https://www.cve.org/CVERecord?id=CVE-2026-53149 Référence CVE CVE-2026-53167 https://www.cve.org/CVERecord?id=CVE-2026-53167 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-53181 https://www.cve.org/CVERecord?id=CVE-2026-53181 Référence CVE CVE-2026-53186 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53093 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53101 https://www.cve.org/CVERecord?id=CVE-2026-53101 Référence CVE CVE-2026-53111 https://www.cve.org/CVERecord?id=CVE-2026-53111 Référence CVE CVE-2026-53112 https://www.cve.org/CVERecord?id=CVE-2026-53112 Référence CVE CVE-2026-53128 https://www.cve.org/CVERecord?id=CVE-2026-53128 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-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-53135 https://www.cve.org/CVERecord?id=CVE-2026-53135 Référence CVE CVE-2026-53136 https://www.cve.org/CVERecord?id=CVE-2026-53136 Référence CVE CVE-2026-53137 https://www.cve.org/CVERecord?id=CVE-2026-53137 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53142 https://www.cve.org/CVERecord?id=CVE-2026-53142 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=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022906LinuxのLinux Kernelにおける有効期限後のメモリの解放の欠如に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。netfilter: nft_fibにおいて、OIFNAMEレジスタを介した古いスタック情報のリークを修正しました。NFT_FIB_RESULT_OIFNAMEの場合、宛先レジスタはlen=IFNAMSIZ（4つの32ビットレジスタ）で宣言されていますが、ルックアップ失敗時やRTN_LOCALおよびoif不一致経路のnft_fib{4,6}_eval()では、「*dest = 0」によって1つのレジスタだけが書き込まれます。残りの3つのレジスタはnft_do_chain()のstruct nft_regsのスタック上にそのまま残されており、レジスタ範囲をロードする下流の式は初期化されていないカーネルスタック情報をユーザースペースへ漏洩させる可能性がありました。NFTA_FIB_F_PRESENTの存在チェックも同様の問題を抱えていました。これはNFT_FIB_RESULT_OIFに対してのみ意味がありますが、任意の結果タイプで受け入れられており、evalはnft_reg_store8()で1バイトのみを書き込み、宣言された範囲の残りは古いままでした。以下の修正が行われています：- eval内の単純な「*dest = 0」を、OIFNAMEの全IFNAMSIZ分をstrscpy_pad()で書き込むnft_fib_store_result()に置き換えました（他の早期リターン経路でも既に使用されています）。- NFTA_FIB_F_PRESENTをNFT_FIB_RESULT_OIFに制限し、宛先を単一のu8として宣言することで、マークされた範囲がevalで書き込まれる1バイトと一致するようにしました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.10, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 8 Sept 2026, 08:50 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-39339
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
    f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 6744e49fe51bfba26522acc2d0e9703cb41d8e50; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < eca18feed38b3377a2ec5d1f22af1170c55d0171; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < d19ddef8c327a4773ff81f8e51027d1e0b4cf069; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < eb8a8124484dbc3c2b543e207da39bbccb703d31; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 8c84885e9790823828bb8084736ea15769b1ac16; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 84d8f58cf28a0415413f43ba7148f7bacd4c1b6e; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 3544210609f6d1db282bbdeca639104ef624c393; f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < ab185e0c4fb82dfba6fb86f8271e06f931d9c64c · Fixed: < 4.10; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.143 ≤ 6.6.*; 6.12.94 ≤ 6.12.*; 6.18.36 ≤ 6.18.*; 7.0.13 ≤ 7.0.*
    After
    Linux: f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 6744e49fe51bfba26522acc2d0e9703cb41d8e50, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < eca18feed38b3377a2ec5d1f22af1170c55d0171, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < d19ddef8c327a4773ff81f8e51027d1e0b4cf069, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < eb8a8124484dbc3c2b543e207da39bbccb703d31, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 8c84885e9790823828bb8084736ea15769b1ac16, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 84d8f58cf28a0415413f43ba7148f7bacd4c1b6e, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < 3544210609f6d1db282bbdeca639104ef624c393, f6d0cbcf09c506b9b022df8f9d7693a7cec3c732 < ab185e0c4fb82dfba6fb86f8271e06f931d9c64c, 4.10 · Fixed: Linux: < 4.10, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 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-39339↗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-53134 · cve.blacktree.nl