Bug 2140883 (CVE-2022-3621) - CVE-2022-3621 kernel: nilfs2: NULL pointer dereference in nilfs_bmap_lookup_at_level in fs/nilfs2/inode.c
Summary: CVE-2022-3621 kernel: nilfs2: NULL pointer dereference in nilfs_bmap_lookup_a...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-3621
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2136784
TreeView+ depends on / blocked
 
Reported: 2022-11-08 03:31 UTC by TEJ RATHI
Modified: 2022-12-21 11:09 UTC (History)
36 users (show)

Fixed In Version: kernel 6.1-rc1
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the NILFS2 file system implementation in the Linux kernel. If the i_mode field in inode of the metadata files is corrupted on the disk, it can cause the initialization of the bmap structure not being called, resulting in a NULL pointer dereference at nilfs_bmap_lookup_at_level. A user permitted to mount arbitrary file system images could use this flaw to cause a denial of service.
Clone Of:
Environment:
Last Closed: 2022-12-21 08:18:34 UTC


Attachments (Terms of Use)

Description TEJ RATHI 2022-11-08 03:31:00 UTC
A vulnerability was found in Linux Kernel. It has been classified as problematic. Affected is the function nilfs_bmap_lookup_at_level of the file fs/nilfs2/inode.c of the component nilfs2. The manipulation leads to null pointer dereference. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-211920.

https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=21a87d88c2253350e115029f14fe2a10a7e6c856
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=21a87d88c2253350e115029f14fe2a10a7e6c856
https://vuldb.com/?id.211920
https://lists.debian.org/debian-lts-announce/2022/11/msg00001.html

Comment 1 Product Security DevOps Team 2022-12-21 08:18:31 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-3621


Note You need to log in before you can comment on or make changes to this bug.