5.5

CVE-2024-46781

nilfs2: fix missing cleanup on rollforward recovery error

In the Linux kernel, the following vulnerability has been resolved:

nilfs2: fix missing cleanup on rollforward recovery error

In an error injection test of a routine for mount-time recovery, KASAN
found a use-after-free bug.

It turned out that if data recovery was performed using partial logs
created by dsync writes, but an error occurred before starting the log
writer to create a recovered checkpoint, the inodes whose data had been
recovered were left in the ns_dirty_files list of the nilfs object and
were not freed.

Fix this issue by cleaning up inodes that have read the recovery data if
the recovery routine fails midway before the log writer starts.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 2.6.30 < 4.19.322
Linux ≫ Linux Kernel Version >= 4.20 < 5.4.284
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.226
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.167
Linux ≫ Linux Kernel Version >= 5.16 < 6.1.110
Linux ≫ Linux Kernel Version >= 6.2 < 6.6.51
Linux ≫ Linux Kernel Version >= 6.7 < 6.10.10
Linux ≫ Linux Kernel Version6.11 Updaterc1
Linux ≫ Linux Kernel Version6.11 Updaterc2
Linux ≫ Linux Kernel Version6.11 Updaterc3
Linux ≫ Linux Kernel Version6.11 Updaterc4
Linux ≫ Linux Kernel Version6.11 Updaterc5
Linux ≫ Linux Kernel Version6.11 Updaterc6
VulnDex Vulnerability Enrichment
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.24% 0.151
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
nvd@nist.gov 5.5 1.8 3.6
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-416 Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

https://git.kernel.org/stable/c/07e4dc2fe000ab008bcfe90be4324ef56b5b4355
Patch
https://git.kernel.org/stable/c/1cf1f7e8cd47244fa947d357ef1f642d91e219a3
Patch
https://git.kernel.org/stable/c/35a9a7a7d94662146396199b0cfd95f9517cdd14
Patch
https://git.kernel.org/stable/c/5787fcaab9eb5930f5378d6a1dd03d916d146622
Patch
https://git.kernel.org/stable/c/8e2d1e9d93c4ec51354229361ac3373058529ec4
Patch
https://git.kernel.org/stable/c/9d8c3a585d564d776ee60d4aabec59b404be7403
Patch
https://git.kernel.org/stable/c/ca92c4bff2833cb30d493b935168d6cccd5c805d
Patch
https://git.kernel.org/stable/c/da02f9eb333333b2e4f25d2a14967cff785ac82e
Patch
https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html