Withdrawn: this CVE is not a vulnerability
The assigning CNA withdrew CVE-2024-56686 on 16 October 2026, and it carries the Rejected state at CVE.org and NVD. It must not be treated as a live finding. Its pre-withdrawal severity, score and exploitability are withheld below; the record itself is kept because withdrawals are reversible and because the reject reason is the correction worth publishing.
CVE-2024-56686
"Apache Linux Kernel ext4 Buffer Overflow Vulnerability"
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
Dec. 28, 2024, 10:15 a.m.
Last Modified :
Oct. 16, 2026, 2:10 p.m.
Remotely Exploit :
—
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Public PoC/Exploit Available at Github
CVE-2024-56686 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
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).
None
JavaScript
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-56686 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-56686 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 Translated by [email protected]
Oct. 16, 2026
Action Type Old Value New Value Changed Translation Title: rechazado, Description: Motivo del rechazo: Este ID de CVE ha sido rechazado o retirado por su Autoridad de Numeración de CVE (CNA). Title: rechazado, Description: Motivo del rechazo: Este ID de CVE ha sido rechazado o retirado por su Autoridad de Numeración de CVE (CNA). -
CVE Translated by [email protected]
Oct. 15, 2026
Action Type Old Value New Value Changed Translation Title: kernel de Linux, Description: En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: corrección de ejecución en la inyección de error de lectura de buffer_head Cuando habilité la depuración de ext4 para las pruebas de inyección de errores, encontré la siguiente advertencia: Error de EXT4-fs (dispositivo sda): ext4_read_inode_bitmap:201: comm fsstress: No se puede leer el mapa de bits del inodo - block_group = 8, inode_bitmap = 1051 ADVERTENCIA: CPU: 0 PID: 511 en fs/buffer.c:1181 mark_buffer_dirty+0x1b3/0x1d0 La causa raíz del problema radica en la implementación incorrecta de la inyección de error de lectura de buffer_head de ext4. La finalización real de la lectura de buffer_head y la inyección de error de buffer_head no son atómicas, lo que puede provocar que el indicador de actualización se borre en los buffer_heads utilizados normalmente en condiciones de ejecución. [CPU0] [CPU1] [CPU2] ext4_read_inode_bitmap ext4_read_bh() ext4_read_inode_bitmap if (buffer_uptodate(bh)) return bh jbd2_journal_commit_transaction __jbd2_journal_refile_buffer __jbd2_journal_unfile_buffer __jbd2_journal_temp_unlink_buffer ext4_simulate_fail_bh() clear_buffer_uptodate mark_buffer_dirty WARN_ON_ONCE(!buffer_uptodate(bh)) El mejor enfoque sería realizar la inyección de fallas en la función de devolución de llamada de finalización de E/S, en lugar de después de la finalización de E/S. Sin embargo, la función de devolución de llamada de finalización de E/S no puede obtener el código de inyección de fallas en sb. Para solucionarlo, pasamos el resultado de la inyección de fallas a la función de lectura de bh. Simulamos fallas dentro de la función de lectura de bh. Esto requiere agregar un parámetro adicional a las funciones de lectura de bh que necesitan la inyección de fallas. Title: rechazado, Description: Motivo del rechazo: Este ID de CVE ha sido rechazado o retirado por su Autoridad de Numeración de CVE (CNA). -
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jan. 07, 2025
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jan. 07, 2025
Action Type Old Value New Value Changed Description In the Linux kernel, the following vulnerability has been resolved: ext4: fix race in buffer_head read fault injection When I enabled ext4 debug for fault injection testing, I encountered the following warning: EXT4-fs error (device sda): ext4_read_inode_bitmap:201: comm fsstress: Cannot read inode bitmap - block_group = 8, inode_bitmap = 1051 WARNING: CPU: 0 PID: 511 at fs/buffer.c:1181 mark_buffer_dirty+0x1b3/0x1d0 The root cause of the issue lies in the improper implementation of ext4's buffer_head read fault injection. The actual completion of buffer_head read and the buffer_head fault injection are not atomic, which can lead to the uptodate flag being cleared on normally used buffer_heads in race conditions. [CPU0] [CPU1] [CPU2] ext4_read_inode_bitmap ext4_read_bh() <bh read complete> ext4_read_inode_bitmap if (buffer_uptodate(bh)) return bh jbd2_journal_commit_transaction __jbd2_journal_refile_buffer __jbd2_journal_unfile_buffer __jbd2_journal_temp_unlink_buffer ext4_simulate_fail_bh() clear_buffer_uptodate mark_buffer_dirty <report warning> WARN_ON_ONCE(!buffer_uptodate(bh)) The best approach would be to perform fault injection in the IO completion callback function, rather than after IO completion. However, the IO completion callback function cannot get the fault injection code in sb. Fix it by passing the result of fault injection into the bh read function, we simulate faults within the bh read function itself. This requires adding an extra parameter to the bh read functions that need fault injection. 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/25a5acf88fed59e060405bbb48098f4a3a2c2adc Removed Reference kernel.org: https://git.kernel.org/stable/c/2f3d93e210b9c2866c8b3662adae427d5bf511ec Removed Reference kernel.org: https://git.kernel.org/stable/c/61832ee7fa2fbd569d129379e795038abfb0d128 Removed Reference kernel.org: https://git.kernel.org/stable/c/77035e4d27e15f87ea55929c8bb8fb1970129e2f -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Dec. 28, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: ext4: fix race in buffer_head read fault injection When I enabled ext4 debug for fault injection testing, I encountered the following warning: EXT4-fs error (device sda): ext4_read_inode_bitmap:201: comm fsstress: Cannot read inode bitmap - block_group = 8, inode_bitmap = 1051 WARNING: CPU: 0 PID: 511 at fs/buffer.c:1181 mark_buffer_dirty+0x1b3/0x1d0 The root cause of the issue lies in the improper implementation of ext4's buffer_head read fault injection. The actual completion of buffer_head read and the buffer_head fault injection are not atomic, which can lead to the uptodate flag being cleared on normally used buffer_heads in race conditions. [CPU0] [CPU1] [CPU2] ext4_read_inode_bitmap ext4_read_bh() <bh read complete> ext4_read_inode_bitmap if (buffer_uptodate(bh)) return bh jbd2_journal_commit_transaction __jbd2_journal_refile_buffer __jbd2_journal_unfile_buffer __jbd2_journal_temp_unlink_buffer ext4_simulate_fail_bh() clear_buffer_uptodate mark_buffer_dirty <report warning> WARN_ON_ONCE(!buffer_uptodate(bh)) The best approach would be to perform fault injection in the IO completion callback function, rather than after IO completion. However, the IO completion callback function cannot get the fault injection code in sb. Fix it by passing the result of fault injection into the bh read function, we simulate faults within the bh read function itself. This requires adding an extra parameter to the bh read functions that need fault injection. Added Reference https://git.kernel.org/stable/c/25a5acf88fed59e060405bbb48098f4a3a2c2adc Added Reference https://git.kernel.org/stable/c/2f3d93e210b9c2866c8b3662adae427d5bf511ec Added Reference https://git.kernel.org/stable/c/61832ee7fa2fbd569d129379e795038abfb0d128 Added Reference https://git.kernel.org/stable/c/77035e4d27e15f87ea55929c8bb8fb1970129e2f