CVE-2022-48877: f2fs: let's avoid panic if extent_tree is not created
Published Aug 21, 2024
·Updated
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected Software
6 affected components
Linux Linux kernel<4.14.304
Linux Linux kernel>=4.15<4.19.271
Linux Linux kernel>=4.20<5.4.230
Linux Linux kernel>=5.5<5.10.165
Linux Linux kernel>=5.11<5.15.90
Linux Linux kernel>=5.16<6.1.8
Event History
Aug 21, 2024
CVE Published
via MITRE·06:10 AM
Rejected
via MITRE·06:10 AM
Data Sourced
via NVD·07:15 AM
Description
Aug 15, 2026
Rejected
via MITRE·12:32 PM
Frequently Asked Questions
1
What is the severity of CVE-2022-48877?
CVE-2022-48877 has not been assigned a specific severity rating, but it addresses a critical kernel panic scenario.
2
How do I fix CVE-2022-48877?
To fix CVE-2022-48877, update your Linux kernel to a version higher than 4.14.304, or within the ranges of 4.15 to 4.19.271, 4.20 to 5.4.230, 5.5 to 5.10.165, 5.11 to 5.15.90, or 5.16 to 6.1.8.
3
Which versions of the Linux kernel are affected by CVE-2022-48877?
CVE-2022-48877 affects Linux kernel versions up to 4.14.304 and specific ranges between versions 4.15 and 6.1.8.
4
What issue does CVE-2022-48877 address?
CVE-2022-48877 addresses a kernel panic encountered when the extent_tree is not created in the f2fs filesystem.
5
Is CVE-2022-48877 specific to a particular Linux distribution?
CVE-2022-48877 is related to the Linux kernel itself and can affect any distribution using the vulnerable kernel versions.