pstore: inode: Only d_invalidate() is needed
Summary
| CVE | CVE-2024-27389 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2024-05-01 13:15:51 UTC |
| Updated | 2026-06-01 17:16:28 UTC |
| Description | 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. --- |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-415
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 d0ee2a8adb6673382cce8a4280e1ca0849b3b783 git | Not specified |
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 db6e5e16f1ee9e3b01d2f71c7f0ba945f4bf0f4e git | Not specified |
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 4cdf9006fc095af71da80e9b5f48a32e991b9ed3 git | Not specified |
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 cb9e802e49c24eeb3af35e9e8c04d526f35f112a git | Not specified |
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 340682ed1932b8e3bd0bfc6c31a0c6354eb57cc6 git | Not specified |
| CNA | Linux | Linux | affected 609e28bb139e53621521130f0d4aea27a725d465 a43e0fc5e9134a46515de2f2f8d4100b74e50de3 git | Not specified |
| CNA | Linux | Linux | affected 5.8 | Not specified |
| CNA | Linux | Linux | unaffected 5.8 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.209 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.83 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.23 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.7.11 6.7.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.8.2 6.8.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.9 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/cb9e802e49c24eeb3af35e9e8c04d526f35f112a | af854a3a-2127-422b-91ae-364da2661108 | git.kernel.org | Patch |
| git.kernel.org/stable/c/db6e5e16f1ee9e3b01d2f71c7f0ba945f4bf0f4e | af854a3a-2127-422b-91ae-364da2661108 | git.kernel.org | Patch |
| git.kernel.org/stable/c/d0ee2a8adb6673382cce8a4280e1ca0849b3b783 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4cdf9006fc095af71da80e9b5f48a32e991b9ed3 | af854a3a-2127-422b-91ae-364da2661108 | git.kernel.org | Patch |
| git.kernel.org/stable/c/340682ed1932b8e3bd0bfc6c31a0c6354eb57cc6 | af854a3a-2127-422b-91ae-364da2661108 | git.kernel.org | Patch |
| git.kernel.org/stable/c/a43e0fc5e9134a46515de2f2f8d4100b74e50de3 | af854a3a-2127-422b-91ae-364da2661108 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.