LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done()

In the Linux kernel, the following vulnerability has been resolved: libceph: prevent potential out-of-bounds reads in handle_auth_done() Perform an explicit bounds check on payload_len to avoid a possible out-of-bounds access in the callout. [ idryomov: changelog ]

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22984 is a Linux kernel libceph flaw where malformed authentication completion data could trigger out-of-bounds reads. The CVSS score is critical, but the source bundle does not show active exploitation. Business risk is highest for systems using Ceph client functionality in the kernel, especially where kernel updates lag.

Executive priority

Treat as high-priority patch validation for Linux fleets using Ceph. The critical score justifies urgency, but prioritization should focus first on confirmed Ceph-exposed systems because the bundle does not prove broad active exploitation.

Technical view

The resolved issue is in libceph handle_auth_done(). The upstream fix adds an explicit bounds check on payload_len before a callout, preventing possible out-of-bounds access. The bundle identifies Linux kernel versions and stable commits, but version applicability should be confirmed against vendor or distribution kernel advisories.

Likely exposure

Likely exposure is Linux systems with kernel Ceph/libceph functionality present and relevant affected kernel builds. The bundle’s affected-version data is not enough to map every distribution kernel precisely.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of exploitation in the wild. The CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction, but exploitability details are not provided.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. Avoid assuming exploit availability, specific attack paths, or all distro impacts without vendor confirmation. The key technical control is bounds validation of payload_len in handle_auth_done().

Mitigation direction

  • Review vendor or distribution advisories for CVE-2026-22984 applicability.
  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Prioritize hosts using Ceph client, RBD, CephFS, or related kernel Ceph features.
  • Apply compensating access controls around Ceph-facing networks where patching is delayed.

Validation and detection

  • Inventory Linux kernel versions across production and exposed infrastructure.
  • Identify systems loading or depending on kernel Ceph/libceph functionality.
  • Compare installed kernels with vendor-fixed builds or referenced stable commits.
  • Confirm post-update kernels are active after reboot or live-patching workflow.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-22984 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-22984Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcd1a677cad994021b19665ed476aea63f5d54f31, cd1a677cad994021b19665ed476aea63f5d54f31, cd1a677cad994021b19665ed476aea63f5d54f31, cd1a677cad994021b19665ed476aea63f5d54f31, cd1a677cad994021b19665ed476aea63f5d54f31, cd1a677cad994021b19665ed476aea63f5d54f31unaffected
LinuxLinux5.11, 0, 5.15.198, 6.1.161, 6.6.121, 6.12.66, 6.18.6, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.