Heimdall Security Logo

CVE-2025-21721

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <7891ac3b0a5c56f7148af507306308ab841cdc31, <=6.12.*, 6.1.131, 2ba466d74ed74f073257f86e61519cb8f8f46184, 0, 6.13.2, <eddd3176b8c4c83a46ab974574cda7c3dfe09388, <ee70999a988b8abc3490609142f50ebaa8344432, <481136234dfe96c7f92770829bec6111c7c5f5dd, 6.14, <=5.10.*, 2.6.30, <=6.6.*, <f70bd2d8ca454e0ed78970f72147ca321dbaa015, 6.6.80, <607dc724b162f4452dc768865e578c1a509a1c8c, <=5.4.*, <2.6.30, 5.4.291, 5.15.179, <1ee2d454baa361d2964e3e2f2cca9ee3f769d93c, <b38c6c260c2415c7f0968871305e7a093daabb4c, 6.12.13, <=*, <=5.15.*, 5.10.235, <=6.13.*

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: handle errors that nilfs_prepare_chunk() may return Patch series "nilfs2: fix issues with rename operations". This series fixes BUG_ON check failures reported by syzbot around rename operations, and a minor behavioral issue where the mtime of a child directory changes when it is renamed instead of moved. This patch (of 2): The directory manipulation routines nilfs_set_link() and nilfs_delete_entry() rewrite the directory entry in the folio/page previously read by nilfs_find_entry(), so error handling is omitted on the assumption that nilfs_prepare_chunk(), which prepares the buffer for rewriting, will always succeed for these. And if an error is returned, it triggers the legacy BUG_ON() checks in each routine. This assumption is wrong, as proven by syzbot: the buffer layer called by nilfs_prepare_chunk() may call nilfs_get_block() if necessary, which may fail due to metadata corruption or other reasons. This has been there all along, but improved sanity checks and error handling may have made it more reproducible in fuzzing tests. Fix this issue by adding missing error paths in nilfs_set_link(), nilfs_delete_entry(), and their caller nilfs_rename().

Gravité et risque d'exploitation

CVE-2025-21721 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.23 %, ce qui la place devant 12.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <7891ac3b0a5c56f7148af507306308ab841cdc31, <=6.12.*, 6.1.131, 2ba466d74ed74f073257f86e61519cb8f8f46184, 0, 6.13.2, <eddd3176b8c4c83a46ab974574cda7c3dfe09388, <ee70999a988b8abc3490609142f50ebaa8344432, <481136234dfe96c7f92770829bec6111c7c5f5dd, 6.14, <=5.10.*, 2.6.30, <=6.6.*, <f70bd2d8ca454e0ed78970f72147ca321dbaa015, 6.6.80, <607dc724b162f4452dc768865e578c1a509a1c8c, <=5.4.*, <2.6.30, 5.4.291, 5.15.179, <1ee2d454baa361d2964e3e2f2cca9ee3f769d93c, <b38c6c260c2415c7f0968871305e7a093daabb4c, 6.12.13, <=*, <=5.15.*, 5.10.235, <=6.13.*) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE