cve.bz

CVE-2026-46008 linux linux kernel: Race Condition

4.7 mediumEPSS 0.09%Fix available

Medium (4.7) in linux linux kernel. EPSS 0.09% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: fix damos_walk() vs kdamond_fn() exit race When kdamond_fn() main loop is finished, the function cancels remaining damos_walk() request and unset the damon_ctx->kdamond so that API callers and API functions themselves can show the context is terminated. damos_walk() adds the caller's request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx->kdamond is set). Only if the kdamond is running, damos_walk() starts waiting for the kdamond's handling of the newly added request. The damos_walk() requests registration and damon_ctx->kdamond unset are protected by different mutexes, though. Hence, damos_walk() could race with damon_ctx->kdamond unset, and result in deadlocks. For example, let's suppose kdamond successfully finished the damow_walk() request cancelling. Right after that, damos_walk() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx->kdamond unset is not yet done. Hence the damos_walk() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a result, the damos_walk() caller thread infinitely waits. Fix this by introducing another damon_ctx field, namely walk_control_obsolete. It is protected by the damon_ctx->walk_control_lock, which protects damos_walk() request registration. Initialize (unset) it in kdamond_fn() before letting damon_start() returns and set it just before the cancelling of the remaining damos_walk() request is executed. damos_walk() reads the obsolete field under the lock and avoids adding a new request. After this change, only requests that are guaranteed to be handled or cancelled are registered. Hence the after-registration DAMON context termination check is no longer needed. Remove it together. The issue is found by sashiko [1].

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.09% (unchanged from 0.09% a week ago; 0.10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46008 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46008?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46008?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46008 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.14 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.58
Linux7.07.0.4
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.0.4-1DEBIAN-CVE-2026-46008
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-46008
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-46008
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-46008
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-46008
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-46008 USN-8569-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 24 moreno fix listedUBUNTU-CVE-2026-46008
Ubuntu25.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-46008
Ubuntu26.04:LTSlinux7.0.0-27.27UBUNTU-CVE-2026-46008 USN-8488-1
Ubuntu26.04:LTSlinux-aws, linux-oem-7.07.0.0-1008.8UBUNTU-CVE-2026-46008 USN-8488-1 USN-8489-1
Ubuntu26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-46008 USN-8603-1
Ubuntu26.04:LTSlinux-gcp, linux-oracle7.0.0-1007.7UBUNTU-CVE-2026-46008 USN-8488-1
Ubuntu26.04:LTSlinux-ibm, linux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-46008 USN-8488-1 USN-8603-1
4 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.0.11-1.1openSUSE-SU-2026:10954-1
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-46008

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46008.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON