5.5

CVE-2023-52566

nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()

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

nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()

In nilfs_gccache_submit_read_data(), brelse(bh) is called to drop the
reference count of bh when the call to nilfs_dat_translate() fails.  If
the reference count hits 0 and its owner page gets unlocked, bh may be
freed.  However, bh->b_page is dereferenced to put the page after that,
which may result in a use-after-free bug.  This patch moves the release
operation after unlocking and putting the page.

NOTE: The function in question is only called in GC, and in combination
with current userland tools, address translation using DAT does not occur
in that function, so the code path that causes this issue will not be
executed.  However, it is possible to run that code path by intentionally
modifying the userland GC library or by calling the GC ioctl directly.

[konishi.ryusuke@gmail.com: NOTE added to the commit log]
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
LinuxLinux Kernel Version >= 2.6.30 < 4.14.327
LinuxLinux Kernel Version >= 4.15 < 4.19.296
LinuxLinux Kernel Version >= 4.20 < 5.4.258
LinuxLinux Kernel Version >= 5.5 < 5.10.198
LinuxLinux Kernel Version >= 5.11 < 5.15.134
LinuxLinux Kernel Version >= 5.16 < 6.1.56
LinuxLinux Kernel Version >= 6.2 < 6.5.6
LinuxLinux Kernel Version6.6 Updaterc1
LinuxLinux Kernel Version6.6 Updaterc2
LinuxLinux Kernel Version6.6 Updaterc3
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.22% 0.125
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
134c704f-9b21-4f2e-91b3-4a467353bcc0 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/193b5a1c6c67c36b430989dc063fe7ea4e200a33
Patch
https://git.kernel.org/stable/c/28df4646ad8b433340772edc90ca709cdefc53e2
Patch
https://git.kernel.org/stable/c/3936e8714907cd55e37c7cc50e50229e4a9042e8
Patch
https://git.kernel.org/stable/c/7130a87ca32396eb9bf48b71a2d42259ae44c6c7
Patch
https://git.kernel.org/stable/c/7ee29facd8a9c5a26079148e36bcf07141b3a6bc
Patch
https://git.kernel.org/stable/c/980663f1d189eedafd18d80053d9cf3e2ceb5c8c
Patch
https://git.kernel.org/stable/c/bb61224f6abc8e71bfdf06d7c984e23460875f5b
Patch
https://git.kernel.org/stable/c/fb1084e63ee56958b0a56e17a50a4fd86445b9c1
Patch