In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix double inode unlock for direct IO sync writes
If we do a direct IO sync write, at btrfs_sync_file(), and we need to skip
inode logging or we get an error starting a transaction or an error when
flushing delalloc, we end up unlocking the inode when we shouldn't under
the 'out_release_extents' label, and then unlock it again at
btrfs_direct_write().
Fix that by checking if we have to skip inode unlocking under that label.
References
Configurations
History
27 Aug 2024, 14:37
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-667 | |
Summary |
|
|
First Time |
Linux
Linux linux Kernel |
|
References | () https://git.kernel.org/stable/c/1a607d22dea4f60438747705495ec4d0af2ec451 - Patch | |
References | () https://git.kernel.org/stable/c/7ba27f14161fc20c4fc0051658a22ddd832eb0aa - Patch | |
References | () https://git.kernel.org/stable/c/8bd4c9220416111500c275546c69c63d42185793 - Patch | |
References | () https://git.kernel.org/stable/c/d924a0be2f218501588cf463d70f1c71afea06d9 - Patch | |
References | () https://git.kernel.org/stable/c/e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 - Patch | |
CPE | cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:* | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
26 Aug 2024, 11:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-08-26 11:15
Updated : 2024-08-27 14:37
NVD link : CVE-2024-43885
Mitre link : CVE-2024-43885
CVE.ORG link : CVE-2024-43885
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking