🛡️ UBUNTU-CVE-2022-49380
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid f2fs_bug_on() in dec_valid_node_count() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215897 I have encountered a bug in F2FS file system in kernel v5.17. The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: The kernel message is shown below: kernel BUG at fs/f2fs/f2fs.h:2511! Call Trace: f2fs_remove_inode_page+0x2a2/0x830 f2fs_evict_inode+0x9b7/0x1510 evict+0x282/0x4e0 do_unlinkat+0x33a/0x540 __x64_sys_unlinkat+0x8e/0xd0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is: .total_valid_block_count or .total_valid_node_count could fuzzed to zero, then once dec_valid_node_count() was called, it will cause BUG_ON(), this patch fixes to print warning info and set SBI_NEED_FSCK into CP instead of panic.

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-02-26
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 5.15.0-47.51
linux-allwinner-5.19
linux-aws 5.15.0-1019.23
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1019.23~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.4 5.4.0-1085.92~18.04.1
linux-aws-5.8
linux-aws-6.2
linux-aws-6.5
linux-aws-fips
linux-aws-hwe
linux-azure 5.15.0-1019.24
linux-azure-4.15
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1019.24~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.4 5.4.0-1091.96~18.04.1
linux-azure-5.8
linux-azure-6.2
linux-azure-6.5
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.15
linux-azure-fde-5.19
linux-azure-fde-6.2
linux-azure-fips
linux-bluefield
linux-fips
linux-gcp 5.15.0-1017.23
linux-gcp-4.15
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1017.23~20.04.2
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.4 5.4.0-1089.97~18.04.1
linux-gcp-5.8
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-fips
linux-gke 5.15.0-1015.18
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 5.15.0-1002.4
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-48.54~20.04.1
linux-hwe-5.19
linux-hwe-5.4 5.4.0-126.142~18.04.1
linux-hwe-5.8
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-edge
linux-ibm 5.15.0-1013.15
linux-ibm-5.4 5.4.0-1033.37~18.04.1
linux-intel-5.13
linux-intel-iot-realtime
linux-intel-iotg 5.15.0-1015.20
linux-intel-iotg-5.15 5.15.0-1015.20~20.04.2
linux-iot 5.4.0-1004.6
linux-kvm 5.15.0-1017.21
linux-lowlatency 5.15.0-47.53
linux-lowlatency-hwe-5.15 5.15.0-48.54~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lts-xenial
linux-nvidia 5.15.0-1007.7
linux-nvidia-6.2
linux-nvidia-6.5
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.5
linux-oracle 5.15.0-1017.22
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1017.22~20.04.1
linux-oracle-5.3
linux-oracle-5.4 5.4.0-1083.91~18.04.1
linux-oracle-5.8
linux-oracle-6.5
linux-raspi 5.15.0-1014.16
linux-raspi-5.4 5.4.0-1070.80~18.04.1
linux-raspi-realtime
linux-raspi2
linux-realtime 5.15.0-1020.20
linux-riscv
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1018.21~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.5
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5

Similar Threats

Vulnerability Monitoring

Stay informed about vulnerabilities in your stack

BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.