pstore: inode: Only d_invalidate() is needed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 609e28bb139e53621521130f0d4aea27a725d465 · < a43e0fc5e9134a46515de2f2f8d4100b74e50de3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pstore: inode: Only d_invalidate() is needed
Unloading a modular pstore backend with records in pstorefs would trigger the dput() double-drop warning:
WARNING: CPU: 0 PID: 2569 at fs/dcache.c:762 dput.part.0+0x3f3/0x410
Using the combo of d_drop()/dput() (as mentioned in Documentation/filesystems/vfs.rst) isn't the right approach here, and leads to the reference counting problem seen above. Use d_invalidate() and update the code to not bother checking for error codes that can never happen.
---
From the CVE record · Linux
The Linux kernel's pstorefs inode handling has a reference-counting issue that can trigger a dput() double-drop warning. It occurs when a modular pstore backend is unloaded while records remain in pstorefs; the input does not establish a separate attack path or authentication requirement.
Engineers running Linux kernels with modular pstore backends should check their systems; affected versions are not specified.