Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-68082 critical CVSS 9.8

Vulnerability in Linux kernel (CVE-2026-68082)

Summary

Vulnerability in Linux kernel (CVE-2026-68082). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

libceph: fix two unsafe bare decodes in decode_lockers()

decode_lockers() in cls_lock_client.c contains two bare decode operations
that allow a malicious or compromised OSD to trigger slab-out-of-bounds
reads:

  1. ceph_decode_32(p) at the num_lockers field has no preceding bounds
    check. ceph_start_decoding() accepts struct_len=0 as valid -- the
    internal ceph_decode_need(p, end, 0, bad) always passes -- so when an
    OSD sends struct_len=0, ceph_start_decoding() returns success with
    p == end. The immediately following bare ceph_decode_32(p) then reads
    4 bytes past the validated buffer boundary. The garbage value is
    passed directly to kzalloc_objs() as the locker count.

    The sibling function decode_watchers() in osd_client.c already uses
    ceph_decode_32_safe() after its own ceph_start_decoding() call.
    decode_lockers() was the only site using the bare variant.

  2. ceph_decode_8(p) after the decode_locker() loop has no preceding
    bounds check. If an OSD crafts num_lockers such that the loop
    advances p exactly to end, the subsequent bare ceph_decode_8(p) reads
    one byte past the validated buffer boundary. The result is passed
    directly into *type, which is used as a lock type discriminator by
    callers, giving an OSD-controlled one-byte OOB read with direct
    influence over the lock type field.

Fix both by replacing bare operations with their safe variants:
ceph_decode_32(p)…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-68082 has been found in Linux kernel.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-68082" on the vendor's site.

CVE-2026-68082 (Linux kernel) — CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"4.9.0"},{"fixed":"5.10.266"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.217"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.184"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.153"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.105"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.46"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details