Look up another CVE · open CVE-2024-36881 in the interactive tracker
CVE-2024-36881
mm/userfaultfd: reset ptes when close() for wr-protected ones
Published 2024-05-30 (2 years ago) by the Linux kernel CNA. Subsystem fs. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2024-36881 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
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No 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 13trixie | fixed | 6.8.11-1 | Update the kernel and reboot. Fixed in 6.8.11-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.8.11-1 | Update the kernel and reboot. Fixed in 6.8.11-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.8.11-1 | Update the kernel and reboot. Fixed in 6.8.11-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Userfaultfd unregister includes a step to remove wr-protect bits from all the relevant pgtable entries, but that only covered an explicit UFFDIO_UNREGISTER ioctl, not a close() on the userfaultfd itself. Cover that too. This fixes a WARN trace. The only user visible side effect is the user can observe leftover wr-protect bits even if the user close()ed on an userfaultfd when releasing the last reference of it. However hopefully that should be harmless, and nothing bad should happen even if so. This change is now more important after the recent page-table-check patch we merged in mm-unstable (446dd9ad37d0 ("mm/page_table_check: support userfault wr-protect entries")), as we'll do sanity check on uffd-wp bits without vma context. So it's better if we can 100% guarantee no uffd-wp bit leftovers, to make sure each report will be valid.
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.
fs/userfaultfd.c
- What this is
- FILESYSTEMS (VFS and infrastructure)MAINTAINERS section matched on fs/* · linux-fsdevel@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_USERFAULTFD /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 builds this code. Every release with an answer below compiles the affected file into the kernels it ships. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixiey
- forky, sid?
- y
- built into the kernel image on every flavour - only a patch removes it
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switch
- CONFIG_USERFAULTFD
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
- 2024-05-30 (2 years ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.24%, higher than 13.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- fs
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.0 | 6.6.31 | 377f3a9a3d03 |
| 6.0 | 6.8.10 | 8d8b68a5b0c9 |
| 6.0 | 6.9 | c88033efe9a3 |
| 5.19.6 | 0 | 0 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2024-36881, 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.