Look up another CVE · open CVE-2025-40217 in the interactive tracker
CVE-2025-40217
pidfs: validate extensible ioctls
Published 2025-12-04 (10 months ago) by the Linux kernel CNA. Subsystem fs. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2025-40217 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 | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | vulnerable | 6.12.113-1 | No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication. |
| Debian 14forky | fixed | 6.17.6-1 | Update the kernel and reboot. Fixed in 6.17.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.17.6-1 | Update the kernel and reboot. Fixed in 6.17.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Validate extensible ioctls stricter than we do now.
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/pidfs.c
include/linux/fs.h
- What this is
- FILESYSTEMS (VFS and infrastructure)MAINTAINERS section matched on fs/* · linux-fsdevel@vger.kernel.org · Maintained
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 1 release, so nothing is claimed about those.
- bookworm?
- trixie, forky, sidy
- ?
- not established - no Makefile entry for the affected file
- y
- built into the kernel image on every flavour - only a patch removes it
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.
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 Debian linux-config packages
Signals
- Published
- 2025-12-04 (10 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.17%, higher than 6.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- 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.11 | 6.17.4 | bf0fbf5e8b0a |
| 6.11 | 6.18 | 3c17001b21b9 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2025-40217, 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.