CVE-2026-99569
Linux kernel removed xattrs can reappear in F2FS roll-forward recovery
An attacker with local access can make removed extended attributes reappear on F2FS files after recovery.
Texto original en inglés · Ver en español
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-99569 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The f2fs file system in the Linux kernel can keep a stale extended-attribute node after roll-forward recovery, so the node block is never freed and removed xattrs can reappear. The problem occurs when a file's xattrs shrink to fit inline and the file is then fsynced without a checkpoint.
Descripción original del registro (Linux)
In the Linux kernel, the following vulnerability has been resolved: f2fs: release a removed xattr node in roll-forward recovery When xattrs shrink enough to fit in the inline xattr area, write_all_xattrs() truncates the xattr node and clears i_xattr_nid. If the file is then fsynced without a checkpoint, only the inode block is written, with i_xattr_nid of 0. Roll-forward recovery starts from the checkpointed inode, whose i_xattr_nid still points to the old xattr node. f2fs_recover_inline_xattr() copies only the inline xattr area, and f2fs_update_inode() writes the old i_xattr_nid back. So the inode keeps the stale xattr node: - The node block is never released, and fsck reports "nonzero bytes in xattr space after end of list". - If the inline xattr list ends exactly at the end of the inline area, its terminator is read from the stale node, and the removed xattrs come back after recovery. When the fsynced inode has no xattr node but the checkpointed one has, release the old xattr node as truncate_node() does: check its block address, invalidate the block and drop its node cache, which may still be dirty.
Versiones afectadas
3.15Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Linux |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://git.kernel.org/stable/c/246a50b23bf2042c77b167272db121d03c8dd473https://git.kernel.org/stable/c/c06cfda3b67692651438876663ae7cdc187eb214https://git.kernel.org/stable/c/6d9c89d6dd18c0cfec33bdb468bf4b86c0ca7ceahttps://git.kernel.org/stable/c/f5924de8867c09206ba631b9faed63862ec00a10Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
