data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-31458 in the interactive tracker

CVE-2026-31458

mm/damon/sysfs: check contexts->nr before accessing contexts_arr[0]

EPSS 0.2%

Published 2026-04-22 (6 months ago) by the Linux kernel CNA. Subsystem mm/damon. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-31458 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixedDSA-6238-1 · 2026-04-30 · text6.12.85-1Update the kernel and reboot. DSA-6238-1 shipped the fix on 2026-04-30, in 6.12.85-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.19.11-1Update the kernel and reboot. Fixed in 6.19.11-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.19.11-1Update the kernel and reboot. Fixed in 6.19.11-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

Multiple sysfs command paths dereference contexts_arr[0] without first verifying that kdamond->contexts->nr == 1. A user can set nr_contexts to 0 via sysfs while DAMON is running, causing NULL pointer dereferences. In more detail, the issue can be triggered by privileged users like below. First, start DAMON and make contexts directory empty (kdamond->contexts->nr == 0). # damo start # cd /sys/kernel/mm/damon/admin/kdamonds/0 # echo 0 > contexts/nr_contexts Then, each of below commands will cause the NULL pointer dereference. # echo update_schemes_stats > state # echo update_schemes_tried_regions > state # echo update_schemes_tried_bytes > state # echo update_schemes_effective_quotas > state # echo update_tuned_intervals > state Guard all commands (except OFF) at the entry point of damon_sysfs_handle_cmd().

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

mm/damon/sysfs.c

What this is
DAMONMAINTAINERS section matched on mm/damon/ · damon@lists.linux.dev · Maintained

Check it on the machine

grep -wE 'CONFIG_DAMON|CONFIG_DAMON_SYSFS' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 1 release. It does build it in 3 releases, so the answer depends on which release the machine runs.

  • bookwormn
  • trixie, forky, sidy
n
not enabled on any flavour - this release does not build the code
y
built into the kernel image on every flavour - only a patch removes it
Build switches
CONFIG_DAMON, CONFIG_DAMON_SYSFS
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-04-22 (6 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.16%, higher than 5.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
mm/damon

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
5.186.6.131aba546061341
5.186.12.801e8da7926724
5.186.18.21708033c231bd
5.186.19.11bbe03ad3fb9e
5.187.01bfe9fb5ed26

Debian advisories

AdvisoryDateShipped toDebian
DSA-6238-12026-04-30trixie 6.12.85-1tracker

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-31458, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.