CVE-2024-43885
Btrfs Double Inode Unlock Vulnerability
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
Aug. 26, 2024, 11:15 a.m.
Last Modified :
Oct. 29, 2024, 2:15 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-43885 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-43885 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 29, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 29, 2024
Action Type Old Value New Value Changed Description 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. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Removed Reference kernel.org https://git.kernel.org/stable/c/1a607d22dea4f60438747705495ec4d0af2ec451 Removed Reference kernel.org https://git.kernel.org/stable/c/8bd4c9220416111500c275546c69c63d42185793 Removed Reference kernel.org https://git.kernel.org/stable/c/7ba27f14161fc20c4fc0051658a22ddd832eb0aa Removed Reference kernel.org https://git.kernel.org/stable/c/d924a0be2f218501588cf463d70f1c71afea06d9 Removed Reference kernel.org https://git.kernel.org/stable/c/e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 Removed CWE NIST CWE-667 Removed CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Removed CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:* -
CVE Translated by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 29, 2024
Action Type Old Value New Value Removed Translation Title: kernel de Linux Description: En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: btrfs: corrige el doble desbloqueo de inodo para escrituras de sincronización de IO directa. Si realizamos una escritura de sincronización de IO directa, en btrfs_sync_file(), y necesitamos omitir el registro de inodo o obtendremos un error al iniciar una transacción o un error al vaciar delalloc, terminamos desbloqueando el inodo cuando no deberíamos bajo la etiqueta 'out_release_extents', y luego lo desbloqueamos nuevamente en btrfs_direct_write(). Solucione eso verificando si tenemos que omitir el desbloqueo de inodos debajo de esa etiqueta. -
Initial Analysis by [email protected]
Aug. 27, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/1a607d22dea4f60438747705495ec4d0af2ec451 No Types Assigned https://git.kernel.org/stable/c/1a607d22dea4f60438747705495ec4d0af2ec451 Patch Changed Reference Type https://git.kernel.org/stable/c/7ba27f14161fc20c4fc0051658a22ddd832eb0aa No Types Assigned https://git.kernel.org/stable/c/7ba27f14161fc20c4fc0051658a22ddd832eb0aa Patch Changed Reference Type https://git.kernel.org/stable/c/8bd4c9220416111500c275546c69c63d42185793 No Types Assigned https://git.kernel.org/stable/c/8bd4c9220416111500c275546c69c63d42185793 Patch Changed Reference Type https://git.kernel.org/stable/c/d924a0be2f218501588cf463d70f1c71afea06d9 No Types Assigned https://git.kernel.org/stable/c/d924a0be2f218501588cf463d70f1c71afea06d9 Patch Changed Reference Type https://git.kernel.org/stable/c/e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 No Types Assigned https://git.kernel.org/stable/c/e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 Patch Added CWE NIST CWE-667 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:* -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 26, 2024
Action Type Old Value New Value Added Description 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. Added Reference kernel.org https://git.kernel.org/stable/c/1a607d22dea4f60438747705495ec4d0af2ec451 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/8bd4c9220416111500c275546c69c63d42185793 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/7ba27f14161fc20c4fc0051658a22ddd832eb0aa [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d924a0be2f218501588cf463d70f1c71afea06d9 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e0391e92f9ab4fb3dbdeb139c967dcfa7ac4b115 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-43885 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-43885
weaknesses.