This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-68165 →
Categories
DEBIAN-CVE-2026-68165

Vulnerability in linux (DEBIAN-CVE-2026-68165)

Summary

Vulnerability in linux (DEBIAN-CVE-2026-68165). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.1.187-1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: validate ranges in damon_set_regions() DAMON core logic assumes zero length regions don't exist. However, a few DAMON API callers including DAMON_SYSFS, DAMON_RECLAIM and DAMON_LRU_SORT allow users to set empty monitoring target regions. This could result in WARN_ONCE() on CONFIG_DAMON_DEBUG_SANITY enabled kernel, and divide-by-zero from damon_merge_two_regions(). For example, the WANR_ONCE() can be triggered like below. # grep DAMON_DEBUG_SANITY /boot/config-$(uname -r) # CONFIG_DAMON_DEBUG_SANITY=y # damo start # cd /sys/kernel/mm/damon/admin/kdamonds/0 # echo 0 > contexts/0/targets/0/regions/0/start # echo 0 > contexts/0/targets/0/regions/0/end # echo commit > state # dmesg [....] [ 73.705780] ------------[ cut here ]------------ [ 73.707552] start 0 >= end 0 [ 73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758 [...] All DAMON API callers eventually use damon_set_regions() to setup the regions. Add the validation logic in the function.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-68165 has been found in linux.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux to 6.1.187-1 or later.
If unsure, ask your IT team or search "linux DEBIAN-CVE-2026-68165" on the vendor's site.

DEBIAN-CVE-2026-68165 (linux)
Patched: 6.1.187-1 — apply immediately
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.

📍 Affected scope

Check the vendor advisory for the affected versions of linux.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.1.187-1.

🛡️ 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. Run grep -r 'linux' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    grep -r 'linux' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade linux to 6.1.187-1

    ステージング環境で 6.1.187-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

Debian:12 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.187-1"}]}]
Debian:13 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.101-1"}]}]
Debian:14 linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.6-1"}]}]
Debian:12 linux-6.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.101-1~deb12u1"}]}]

References

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