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

bpf: Fix ld_{abs,ind} failure path analysis in subprogs

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 19 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

25 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.101-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 7 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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.

1 current
CVE-2026-53090 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2026-53090
151 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-38958

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

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: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

Why

The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.

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: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

Why

The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.

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 → Incorrect Check of Function Return Value → 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-253 ↗

CWE-253: Incorrect Check of Function Return Value. The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-38958Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix ld_{abs,ind} failure path analysis in subprogs Usage of ld_{abs,ind} instructions got extended into subprogs some time ago via commit 09b28d76eac4 ("bpf: Add abnormal return checks."). These are only allowed in subprograms when the latter are BTF annotated and have scalar return types. The code generator in bpf_gen_ld_abs() has an abnormal exit path (r0=0 + exit) from legacy cBPF times. While the enforcement is on scalar return types, the verifier must also simulate the path of abnormal exit if the packet data load via ld_{abs,ind} failed. This is currently not the case. Fix it by having the verifier simulate both success and failure paths, and extend it in similar ways as we do for tail calls. The success path (r0=unknown, continue to next insn) is pushed onto stack for later validation and the r0=0 and return to the caller is done on the fall-through side.

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-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 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-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 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-53024 Référence CVE CVE-2026-53025 https://www.cve.org/CVERecord?id=CVE-2026-53025 Référence CVE CVE-2026-53043 https://www.cve.org/CVERecord?id=CVE-2026-53043 Référence CVE CVE-2026-53045 https://www.cve.org/CVERecord?id=CVE-2026-53045 Référence CVE CVE-2026-53053 https://www.cve.org/CVERecord?id=CVE-2026-53053 Référence CVE CVE-2026-53070 https://www.cve.org/CVERecord?id=CVE-2026-53070 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23394 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-45963 https://www.cve.org/CVERecord?id=CVE-2026-45963 Référence CVE CVE-2026-46111 https://www.cve.org/CVERecord?id=CVE-2026-46111 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53361 https://www.cve.org/CVERecord?id=CVE-2026-53361 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64139 https://www.cve.org/CVERecord?id=CVE-2026-64139 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64270 https://www.cve.org/CVERecord?id=CVE-2026-64270 Référence CVE CVE-2026-64272 https://www.cve.org/CVERecord?id=CVE-2026-64272 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64294 https://www.cve.org/CVERecord?id=

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

, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS msg00035 du 18 août 2026 https://lists.debian.org/debian-lts-announce/2026/08/msg00035.html Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2026-45897 https://www.cve.org/CVERecord?id=CVE-2026-45897 Référence CVE CVE-2026-45901 https://www.cve.org/CVERecord?id=CVE-2026-45901 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 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-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=

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

es, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian msg00326 du 06 août 2026 https://lists.debian.org/debian-security-announce/2026/msg00326.html Référence CVE CVE-2025-40098 https://www.cve.org/CVERecord?id=CVE-2025-40098 Référence CVE CVE-2026-45897 https://www.cve.org/CVERecord?id=CVE-2026-45897 Référence CVE CVE-2026-45901 https://www.cve.org/CVERecord?id=CVE-2026-45901 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-64205 https://www.cve.org/CVERecord?id=CVE-2026-64205 Référence CVE CVE-2026-64280 https://www.cve.org/CVERecord?id=CVE-2026-64280 Référence CVE CVE-2026-64290 https://www.cve.org/CVERecord?id=CVE-2026-64290 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64562 https://www.cve.org/CVERecord?id=CVE-2026-64562 Référence CVE CVE-2026-64563 https://www.cve.org/CVERecord?id=CVE-2026-64563 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64565 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-53041 Référence CVE CVE-2026-53049 https://www.cve.org/CVERecord?id=CVE-2026-53049 Référence CVE CVE-2026-53050 https://www.cve.org/CVERecord?id=CVE-2026-53050 Référence CVE CVE-2026-53053 https://www.cve.org/CVERecord?id=CVE-2026-53053 Référence CVE CVE-2026-53060 https://www.cve.org/CVERecord?id=CVE-2026-53060 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53103 https://www.cve.org/CVERecord?id=CVE-2026-53103 Référence CVE CVE-2026-53122 https://www.cve.org/CVERecord?id=CVE-2026-53122 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 Référence CVE CVE-2026-53139 https://www.cve.org/CVERecord?id=CVE-2026-53139 Référence CVE CVE-2026-53156 https://www.cve.org/CVERecord?id=CVE-2026-53156 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-53176 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-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 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-53070 Référence CVE CVE-2026-53071 https://www.cve.org/CVERecord?id=CVE-2026-53071 Référence CVE CVE-2026-53072 https://www.cve.org/CVERecord?id=CVE-2026-53072 Référence CVE CVE-2026-53073 https://www.cve.org/CVERecord?id=CVE-2026-53073 Référence CVE CVE-2026-53075 https://www.cve.org/CVERecord?id=CVE-2026-53075 Référence CVE CVE-2026-53078 https://www.cve.org/CVERecord?id=CVE-2026-53078 Référence CVE CVE-2026-53080 https://www.cve.org/CVERecord?id=CVE-2026-53080 Référence CVE CVE-2026-53081 https://www.cve.org/CVERecord?id=CVE-2026-53081 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?id=CVE-2026-53090 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=CVE-2026-53098 Référence CVE CVE-2026-53103 https://www.cve.org/CVERecord?id=CVE-2026-53103 Référence CVE CVE-2026-53112 https://www.cve.org/CVERecord?id=CVE-2026-53112 Référence CVE CVE-2026-53122 https://www.cve.org/CVERecord?id=CVE-2026-53122 Référence CVE CVE-2026-53133 https://www.cve.org/CVERecord?id=CVE-2026-53133 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=

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

d?id=CVE-2026-53081 Référence CVE CVE-2026-53082 https://www.cve.org/CVERecord?id=CVE-2026-53082 Référence CVE CVE-2026-53083 https://www.cve.org/CVERecord?id=CVE-2026-53083 Référence CVE CVE-2026-53084 https://www.cve.org/CVERecord?id=CVE-2026-53084 Référence CVE CVE-2026-53085 https://www.cve.org/CVERecord?id=CVE-2026-53085 Référence CVE CVE-2026-53086 https://www.cve.org/CVERecord?id=CVE-2026-53086 Référence CVE CVE-2026-53087 https://www.cve.org/CVERecord?id=CVE-2026-53087 Référence CVE CVE-2026-53088 https://www.cve.org/CVERecord?id=CVE-2026-53088 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53090 https://www.cve.org/CVERecord?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-53092 https://www.cve.org/CVERecord?id=CVE-2026-53092 Référence CVE CVE-2026-53093 https://www.cve.org/CVERecord?id=CVE-2026-53093 Référence CVE CVE-2026-53094 https://www.cve.org/CVERecord?id=CVE-2026-53094 Référence CVE CVE-2026-53095 https://www.cve.org/CVERecord?id=CVE-2026-53095 Référence CVE CVE-2026-53096 https://www.cve.org/CVERecord?id=CVE-2026-53096 Référence CVE CVE-2026-53097 https://www.cve.org/CVERecord?id=CVE-2026-53097 Référence CVE CVE-2026-53098 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-025024LinuxのLinux Kernelにおける関数の戻り値に対する不適切なチェックに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：bpf: サブプログラム内での ld_{abs,ind} 失敗パス解析の修正。ld_{abs,ind} 命令の使用は、以前にコミット09b28d76eac4（"bpf: Add abnormal return checks."）を通じてサブプログラムに拡張されました。これらは、サブプログラムがBTF注釈されており、かつスカラー型の戻り値を持つ場合にのみ許可されています。bpf_gen_ld_abs() のコードジェネレータには、従来の cBPF 時代から異常終了パス（r0=0 + exit）が存在しています。スカラー戻り値型での制限がある一方で、検証器は ld_{abs,ind} によるパケットデータの読み込みが失敗した場合の異常終了パスもシミュレートしなければなりません。しかし現在はこれが行われていません。そこで、成功パスと失敗パスの両方を検証器がシミュレートするように修正し、テイルコールの場合と同様の方法で拡張しました。成功パス（r0=不明、次の命令に進む）は後で検証するためスタックにプッシュされ、r0=0 として呼び出し元に戻る処理はフォールスルー側で行われます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.10, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 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 24 Jun 2026 · Last source change 19 Aug 2026, 16:28 UTC · CWE-253 · Incorrect Check of Function Return Value

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-38958
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
    09b28d76eac48e922dc293da1aa2b2b85c32aeee < 37ad2bb11e9de92cb7b94548705eeedd87f7d392; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < 8674e2db06cff6b50f2216eed9a761d15425bb34; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < d846d83bdacbd8f14fc45c63b8c1d22608452e1c; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < ee861486e377edc55361c08dcbceab3f6b6577bd; 5.10 · Fixed: < 5.10; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.0.10 ≤ 7.0.*; 7.1 ≤ *
    After
    09b28d76eac48e922dc293da1aa2b2b85c32aeee < 928d354ae3557e8f755a227e67be88034eb3cd7f; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < de1055e7f9e67af32b1f3376066272b04e5223c0; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < 37ad2bb11e9de92cb7b94548705eeedd87f7d392; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < 8674e2db06cff6b50f2216eed9a761d15425bb34; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < d846d83bdacbd8f14fc45c63b8c1d22608452e1c; 09b28d76eac48e922dc293da1aa2b2b85c32aeee < ee861486e377edc55361c08dcbceab3f6b6577bd · Fixed: < 5.10; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.0.10 ≤ 7.0.*
    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-38958↗Vendor CSAF · SUSE Product Security Team↗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-53090 · cve.blacktree.nl