CVE-2022-49699: filemap: Handle sibling entries in filemap_get_read_batch()
Published Feb 26, 2025
·Updated
filemap: Handle sibling entries in filemapgetreadbatch()
Affected Software
6 affected components
Linux Linux kernel
Linux Linux kernel>=5.12<5.18.8
Linux Linux kernel=5.19-rc1
Linux Linux kernel=5.19-rc2
Linux Linux kernel=5.19-rc3
Microsoft cbl2 kernel 5.15.186.1-1
Remediation
Event History
Feb 26, 2025
CVE Published
via MITRE·02:24 AM
Data Sourced
via MITRE·02:24 AM
Description
Data Sourced
via NVD·07:01 AM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 26, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:01 AM
Affected Software
Updated
via Microsoft·01:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2022-49699?
The severity of CVE-2022-49699 is classified as medium, as it involves a race condition that could potentially lead to memory corruption.
2
How do I fix CVE-2022-49699?
To fix CVE-2022-49699, you should update to the latest version of the Linux kernel where the vulnerability has been patched.
3
What types of systems are affected by CVE-2022-49699?
CVE-2022-49699 affects all supported versions of the Linux kernel that utilize the filemap_get_read_batch() function.
4
What could an attacker exploit in CVE-2022-49699?
An attacker could exploit CVE-2022-49699 to potentially manipulate race conditions that could lead to unexpected behavior or crashes.
5
Is CVE-2022-49699 related to any specific Linux kernel versions?
CVE-2022-49699 affects multiple versions of the Linux kernel; therefore, checking for updates or security patches is recommended.