CVE-2025-38282: Linux kernel · kernfs: Relax constraint in draining guard
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 72275c888f8962b406ee9c6885c79bf68cca5a63 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:19 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in 72275c888f8962b406ee9c6885c79bf68cca5a63, 071d8e4c2a3b0999a9b822e2eb8854784a350f8a, 6c81f1c7812c61f187bed1b938f1d2e391d503ab +2
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: kernfs: Relax constraint in draining guard The active reference lifecycle provides the break/unbreak mechanism but the active reference is not truly active after unbreak -- callers don't use it afterwards but it's important for proper pairing of kn->active counting. Assuming this mechanism is in place, the WARN check in kernfs_should_drain_open_files() is too sensitive -- it may transiently catch those (rightful) callers between kernfs_unbreak_active_protection() and kernfs_put_active() as found out by Chen Ridong: kernfs_remove_by_name_ns kernfs_get_active // active=1 __kernfs_remove // active=0x80000002 kernfs_drain ... wait_event //waiting (active == 0x80000001) kernfs_break_active_protection // active = 0x80000001 // continue kernfs_unbreak_active_protection // active = 0x80000002 ... kernfs_should_drain_open_files // warning occurs kernfs_put_active To avoid the false positives (mind panic_on_warn) remove the check altogether. (This is meant as quick fix, I think active reference break/unbreak may be simplified with larger rework.)
References
- git.kernel.org/stable/c/2d6a67c2b3b87808a347dc1047b520a9dd177a4f (opens in a new tab)
- git.kernel.org/stable/c/6c81f1c7812c61f187bed1b938f1d2e391d503ab (opens in a new tab)
- git.kernel.org/stable/c/6bfb154f95d5f0ab7ed056f23aba8c1a94cb3927 (opens in a new tab)
- git.kernel.org/stable/c/72275c888f8962b406ee9c6885c79bf68cca5a63 (opens in a new tab)
- git.kernel.org/stable/c/071d8e4c2a3b0999a9b822e2eb8854784a350f8a (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)