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

libceph: define and enforce CEPH_MAX_KEY_LEN

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 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 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.74% 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-43304 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2026-43304
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: libceph: define and enforce CEPH_MAX_KEY_LEN When decoding the key, verify that the key material would fit into a fixed-size buffer in process_auth_done() and generally has a sane length. The new CEPH_MAX_KEY_LEN check replaces the existing check for a key with no key material which is a) not universal since CEPH_CRYPTO_NONE has to be excluded and b) doesn't provide much value since a smaller than needed key is just as invalid as no key -- this has to be handled elsewhere anyway.
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-28574

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 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: libceph: define and enforce CEPH_MAX_KEY_LEN When decoding the key, verify that the key material would fit into a fixed-size buffer in process_auth_done() and generally has a sane length. The new CEPH_MAX_KEY_LEN check replaces the existing check for a key with no key material which is a) not universal since CEPH_CRYPTO_NONE has to be excluded and b) doesn't provide much value since a smaller than needed key is just as invalid as no key -- this has to be handled elsewhere anyway.

What

In the Linux kernel, the following vulnerability has been resolved: libceph: define and enforce CEPH_MAX_KEY_LEN When decoding the key, verify that the key material would fit into a fixed-size buffer in process_auth_done() and generally has a sane length. The new CEPH_MAX_KEY_LEN check replaces the existing check for a key with no key material which is a) not universal since CEPH_CRYPTO_NONE has to be excluded and b) doesn't provide much value since a smaller than needed key is just as invalid as no key -- this has to be handled elsewhere anyway.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: libceph: define and enforce CEPH_MAX_KEY_LEN When decoding the key, verify that the key material would fit into a fixed-size buffer in process_auth_done() and generally has a sane length. The new CEPH_MAX_KEY_LEN check replaces the existing check for a key with no key material which is a) not universal since CEPH_CRYPTO_NONE has to be excluded and b) doesn't provide much value since a smaller than needed key is just as invalid as no key -- this has to be handled elsewhere anyway.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
NetworkUnauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1454Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260513Security Bulletin 13 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 May 2026, published on 13 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-43279 Référence CVE CVE-2026-43281 https://www.cve.org/CVERecord?id=CVE-2026-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43315 https://www.cve.org/CVERecord?id=CVE-2026-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43324 https://www.cve.org/CVERecord?id=CVE-2026-43324 Référence CVE CVE-2026-43327 https://www.cve.org/CVERecord?id=CVE-2026-43327 Référence CVE CVE-2026-43328 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-43281 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43293 https://www.cve.org/CVERecord?id=CVE-2026-43293 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43306 https://www.cve.org/CVERecord?id=CVE-2026-43306 Référence CVE CVE-2026-43307 https://www.cve.org/CVERecord?id=CVE-2026-43307 Référence CVE CVE-2026-43308 https://www.cve.org/CVERecord?id=CVE-2026-43308 Référence CVE CVE-2026-43309 https://www.cve.org/CVERecord?id=CVE-2026-43309 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43316 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-43240 Référence CVE CVE-2026-43248 https://www.cve.org/CVERecord?id=CVE-2026-43248 Référence CVE CVE-2026-43253 https://www.cve.org/CVERecord?id=CVE-2026-43253 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43294 https://www.cve.org/CVERecord?id=CVE-2026-43294 Référence CVE CVE-2026-43298 https://www.cve.org/CVERecord?id=CVE-2026-43298 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43336 https://www.cve.org/CVERecord?id=CVE-2026-43336 Référence CVE CVE-2026-43337 https://www.cve.org/CVERecord?id=CVE-2026-43337 Référence CVE CVE-2026-43339 https://www.cve.org/CVERecord?id=CVE-2026-43339 Référence CVE CVE-2026-43345 https://www.cve.org/CVERecord?id=CVE-2026-43345 Référence CVE CVE-2026-43351 https://www.cve.org/CVERecord?id=CVE-2026-43351 Référence CVE CVE-2026-43366 https://www.cve.org/CVERecord?id=CVE-2026-43366 Référence CVE CVE-2026-43373 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-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43315 https://www.cve.org/CVERecord?id=CVE-2026-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43317 https://www.cve.org/CVERecord?id=CVE-2026-43317 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 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-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43294 https://www.cve.org/CVERecord?id=CVE-2026-43294 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43298 https://www.cve.org/CVERecord?id=CVE-2026-43298 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=CVE-2026-43319 Référence CVE CVE-2026-43320 https://www.cve.org/CVERecord?id=CVE-2026-43320 Référence CVE CVE-2026-43324 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-43281 Référence CVE CVE-2026-43283 https://www.cve.org/CVERecord?id=CVE-2026-43283 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43287 https://www.cve.org/CVERecord?id=CVE-2026-43287 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43315 https://www.cve.org/CVERecord?id=CVE-2026-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43324 https://www.cve.org/CVERecord?id=CVE-2026-43324 Référence CVE CVE-2026-43327 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43038 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43185 https://www.cve.org/CVERecord?id=CVE-2026-43185 Référence CVE CVE-2026-43186 https://www.cve.org/CVERecord?id=CVE-2026-43186 Référence CVE CVE-2026-43197 https://www.cve.org/CVERecord?id=CVE-2026-43197 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43341 https://www.cve.org/CVERecord?id=CVE-2026-43341 Référence CVE CVE-2026-43376 https://www.cve.org/CVERecord?id=CVE-2026-43376 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43384 https://www.cve.org/CVERecord?id=CVE-2026-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43315 https://www.cve.org/CVERecord?id=CVE-2026-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43317 https://www.cve.org/CVERecord?id=CVE-2026-43317 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43287 Référence CVE CVE-2026-43288 https://www.cve.org/CVERecord?id=CVE-2026-43288 Référence CVE CVE-2026-43289 https://www.cve.org/CVERecord?id=CVE-2026-43289 Référence CVE CVE-2026-43291 https://www.cve.org/CVERecord?id=CVE-2026-43291 Référence CVE CVE-2026-43295 https://www.cve.org/CVERecord?id=CVE-2026-43295 Référence CVE CVE-2026-43296 https://www.cve.org/CVERecord?id=CVE-2026-43296 Référence CVE CVE-2026-43297 https://www.cve.org/CVERecord?id=CVE-2026-43297 Référence CVE CVE-2026-43300 https://www.cve.org/CVERecord?id=CVE-2026-43300 Référence CVE CVE-2026-43302 https://www.cve.org/CVERecord?id=CVE-2026-43302 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=CVE-2026-43304 Référence CVE CVE-2026-43312 https://www.cve.org/CVERecord?id=CVE-2026-43312 Référence CVE CVE-2026-43313 https://www.cve.org/CVERecord?id=CVE-2026-43313 Référence CVE CVE-2026-43314 https://www.cve.org/CVERecord?id=CVE-2026-43314 Référence CVE CVE-2026-43315 https://www.cve.org/CVERecord?id=CVE-2026-43315 Référence CVE CVE-2026-43316 https://www.cve.org/CVERecord?id=CVE-2026-43316 Référence CVE CVE-2026-43317 https://www.cve.org/CVERecord?id=CVE-2026-43317 Référence CVE CVE-2026-43318 https://www.cve.org/CVERecord?id=CVE-2026-43318 Référence CVE CVE-2026-43319 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015887LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルの以下の脆弱性が修正されました：libcephのCEPH_MAX_KEY_LENの定義および強制に関する問題です。キーをデコードする際、process_auth_done()内の固定サイズバッファにキー素材が収まっていること、また一般的に適切な長さであることを検証します。新しいCEPH_MAX_KEY_LENのチェックは既存のキー素材がないキーのチェックに代わるものであり、a) CEPH_CRYPTO_NONEを除外する必要があるため普遍的ではなく、b) 必要な長さより短いキーはキー素材がない場合と同様に無効であり、それは他の場所で処理されるべきであるため、あまり意味を持たないという問題を解決します。

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.11, 5.15.202 ≤ 5.15.*, 6.1.165 ≤ 6.1.*, 6.6.128 ≤ 6.6.*, 6.12.75 ≤ 6.12.*, 6.18.16 ≤ 6.18.*, 6.19.6 ≤ 6.19.*, 7.0 ≤ *
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 8 May 2026 · Last source change 5 Aug 2026, 12:27 UTC · CWE not yet assigned

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-28574
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-28574↗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-43304 · cve.blacktree.nl