{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-04-14T20:57:28.149","vulnerabilities":[{"cve":{"id":"CVE-2025-23132","sourceIdentifier":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","published":"2025-04-16T15:16:07.630","lastModified":"2025-11-04T17:01:21.487","vulnStatus":"Analyzed","cveTags":[],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: quota: fix to avoid warning in dquot_writeback_dquots()\n\nF2FS-fs (dm-59): checkpoint=enable has some unwritten data.\n\n------------[ cut here ]------------\nWARNING: CPU: 6 PID: 8013 at fs\/quota\/dquot.c:691 dquot_writeback_dquots+0x2fc\/0x308\npc : dquot_writeback_dquots+0x2fc\/0x308\nlr : f2fs_quota_sync+0xcc\/0x1c4\nCall trace:\ndquot_writeback_dquots+0x2fc\/0x308\nf2fs_quota_sync+0xcc\/0x1c4\nf2fs_write_checkpoint+0x3d4\/0x9b0\nf2fs_issue_checkpoint+0x1bc\/0x2c0\nf2fs_sync_fs+0x54\/0x150\nf2fs_do_sync_file+0x2f8\/0x814\n__f2fs_ioctl+0x1960\/0x3244\nf2fs_ioctl+0x54\/0xe0\n__arm64_sys_ioctl+0xa8\/0xe4\ninvoke_syscall+0x58\/0x114\n\ncheckpoint and f2fs_remount may race as below, resulting triggering warning\nin dquot_writeback_dquots().\n\natomic write                                    remount\n                                                - do_remount\n                                                 - down_write(&sb->s_umount);\n                                                  - f2fs_remount\n- ioctl\n - f2fs_do_sync_file\n  - f2fs_sync_fs\n   - f2fs_write_checkpoint\n    - block_operations\n     - locked = down_read_trylock(&sbi->sb->s_umount)\n       : fail to lock due to the write lock was held by remount\n                                                 - up_write(&sb->s_umount);\n     - f2fs_quota_sync\n      - dquot_writeback_dquots\n       - WARN_ON_ONCE(!rwsem_is_locked(&sb->s_umount))\n       : trigger warning because s_umount lock was unlocked by remount\n\nIf checkpoint comes from mount\/umount\/remount\/freeze\/quotactl, caller of\ncheckpoint has already held s_umount lock, calling dquot_writeback_dquots()\nin the context should be safe.\n\nSo let's record task to sbi->umount_lock_holder, so that checkpoint can\nknow whether the lock has held in the context or not by checking current\nw\/ it.\n\nIn addition, in order to not misrepresent caller of checkpoint, we should\nnot allow to trigger async checkpoint for those callers: mount\/umount\/remount\/\nfreeze\/quotactl."},{"lang":"es","value":"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: f2fs: cuota: corrección para evitar advertencias en dquot_writeback_dquots() F2FS-fs (dm-59): checkpoint=enable tiene algunos datos no escritos. ------------[ cortar aquí ]------------ ADVERTENCIA: CPU: 6 PID: 8013 en fs\/quota\/dquot.c:691 dquot_writeback_dquots+0x2fc\/0x308 pc : dquot_writeback_dquots+0x2fc\/0x308 lr : f2fs_quota_sync+0xcc\/0x1c4 Rastreo de llamadas: dquot_writeback_dquots+0x2fc\/0x308 f2fs_quota_sync+0xcc\/0x1c4 f2fs_write_checkpoint+0x3d4\/0x9b0 f2fs_issue_checkpoint+0x1bc\/0x2c0 f2fs_sync_fs+0x54\/0x150 f2fs_do_sync_file+0x2f8\/0x814 __f2fs_ioctl+0x1960\/0x3244 f2fs_ioctl+0x54\/0xe0 __arm64_sys_ioctl+0xa8\/0xe4 evolve_syscall+0x58\/0x114 el punto de control y f2fs_remount pueden competir como se muestra a continuación, lo que activa una advertencia en dquot_writeback_dquots(). remot de escritura atómica - do_remount - down_write(&sb->s_umount); - f2fs_remount - ioctl - f2fs_do_sync_file - f2fs_sync_fs - f2fs_write_checkpoint - block_operations - locking = down_read_trylock(&sbi->sb->s_umount) : no se pudo bloquear debido a que el bloqueo de escritura fue mantenido por el remot - up_write(&sb->s_umount); - f2fs_quota_sync - dquot_writeback_dquots - WARN_ON_ONCE(!rwsem_is_locked(&sb->s_umount)) : activa una advertencia porque el bloqueo s_umount se desbloqueó al volver a montar Si el punto de control proviene de mount\/umount\/remount\/freeze\/quotactl, el llamador del punto de control ya ha mantenido el bloqueo s_umount, llamar a dquot_writeback_dquots() en el contexto debería ser seguro. Así que grabemos la tarea en sbi->umount_lock_holder, para que el punto de control pueda saber si el bloqueo se ha mantenido en el contexto o no al verificar la corriente con él. Además, para no tergiversar la llamada del punto de control, no deberíamos permitir que se active el punto de control asíncrono para esos llamadores: mount\/umount\/remount\/freeze\/quotactl."}],"metrics":{"cvssMetricV31":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1\/AV:L\/AC:L\/PR:L\/UI:N\/S:U\/C:N\/I:N\/A:H","baseScore":5.5,"baseSeverity":"MEDIUM","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":3.6}]},"weaknesses":[{"source":"nvd@nist.gov","type":"Primary","description":[{"lang":"en","value":"NVD-CWE-noinfo"}]}],"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.20","versionEndExcluding":"6.14.2","matchCriteriaId":"0B6A4F63-7CAB-44BC-9A23-0264D67B5F15"}]}]}],"references":[{"url":"https:\/\/git.kernel.org\/stable\/c\/d7acf0a6c87aa282c86a36dbaa2f92fda88c5884","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"]},{"url":"https:\/\/git.kernel.org\/stable\/c\/eb85c2410d6f581e957cd03a644ff6ddbe592af9","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"]}]}}]}