CVE-2022-48635: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: fsdax: Fix infinite loop in dax_iomap_rw() I got an infinite loop and a WARNING report when executing a tail command in virtiofs. WARNING: CPU: 10 PID: 964 at fs/iomap/iter.c:34 iomap_iter+0x3a2/0x3d0 Modules linked in: CPU: 10 PID: 964 Comm: tail Not tainted 5.19.0-rc7 Call Trace: <TASK> dax_iomap_rw+0xea/0x620 ? __this_cpu_preempt_check+0x13/0x20 fuse_dax_read_iter+0x47/0x80 fuse_file_read_iter+0xae/0xd0 new_sync_read+0xfe/0x180 ? 0xffffffff81000000 vfs_read+0x14d/0x1a0 ksys_read+0x6d/0xf0 __x64_sys_read+0x1a/0x20 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The tail command will call read() with a count of 0. In this case, iomap_iter() will report this WARNING, and always return 1 which casuing the infinite loop in dax_iomap_rw(). Fixing by checking count whether is 0 in dax_iomap_rw().
AI Analysis
Technical Summary
CVE-2022-48635 is a medium-severity vulnerability in the Linux kernel affecting the fsdax subsystem, specifically in the dax_iomap_rw() function. The flaw manifests as an infinite loop triggered when the read() system call is invoked with a count of zero, such as when using the 'tail' command on virtiofs. Internally, iomap_iter() incorrectly returns 1 when the count is zero, causing dax_iomap_rw() to loop indefinitely. This results in a CPU warning and potential resource exhaustion. The vulnerability stems from improper handling of zero-length reads in the dax_iomap_rw() function, violating expected iteration behavior. The fix involves adding a check to handle zero count values correctly, preventing the infinite loop. The vulnerability is classified under CWE-835 (Loop with Unreachable Exit Condition) and has a CVSS 3.1 base score of 6.2, indicating a medium severity with local attack vector, low complexity, no privileges required, no user interaction, unchanged scope, and impact limited to availability (denial of service). No known exploits are currently reported in the wild. The affected Linux kernel versions include the commit identified by ca289e0b95afa973d204c77a4ad5c37e06145fbf and likely other versions prior to the patch. This vulnerability primarily impacts systems using the fsdax and virtiofs features, which are relevant in environments leveraging persistent memory and virtualized file systems, respectively.
Potential Impact
For European organizations, the impact of CVE-2022-48635 centers on potential denial-of-service conditions on Linux systems utilizing fsdax and virtiofs. Such systems are often found in data centers, cloud infrastructure, and virtualization platforms that employ persistent memory technologies or advanced file system features. An infinite loop in kernel space can lead to CPU resource exhaustion, degraded system performance, or crashes, potentially disrupting critical services. While the vulnerability does not compromise confidentiality or integrity, availability impacts could affect high-availability environments, financial services, telecommunications, and public sector infrastructure relying on Linux-based virtualization. The local attack vector and absence of required privileges limit exploitation to users or processes with local access, reducing remote attack risks but increasing concerns in multi-tenant or shared environments. European organizations with virtualized workloads or persistent memory deployments should assess exposure, as denial-of-service conditions could lead to operational downtime and associated financial or reputational damage.
Mitigation Recommendations
To mitigate CVE-2022-48635, European organizations should: 1) Apply the latest Linux kernel patches that include the fix for the infinite loop in dax_iomap_rw(), ensuring kernel versions are updated beyond the commit ca289e0b95afa973d204c77a4ad5c37e06145fbf. 2) Audit systems for usage of fsdax and virtiofs features, particularly in virtualized or persistent memory environments, to identify potentially vulnerable hosts. 3) Limit local user access to trusted personnel and processes, as exploitation requires local interaction with the read() syscall on affected filesystems. 4) Implement monitoring for unusual CPU usage or kernel warnings related to iomap_iter or dax_iomap_rw to detect potential exploitation attempts or system instability. 5) In environments where immediate patching is not feasible, consider disabling fsdax or virtiofs features if not critical to operations, to reduce attack surface. 6) Incorporate this vulnerability into incident response and vulnerability management workflows to ensure timely detection and remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Ireland, Belgium
CVE-2022-48635: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: fsdax: Fix infinite loop in dax_iomap_rw() I got an infinite loop and a WARNING report when executing a tail command in virtiofs. WARNING: CPU: 10 PID: 964 at fs/iomap/iter.c:34 iomap_iter+0x3a2/0x3d0 Modules linked in: CPU: 10 PID: 964 Comm: tail Not tainted 5.19.0-rc7 Call Trace: <TASK> dax_iomap_rw+0xea/0x620 ? __this_cpu_preempt_check+0x13/0x20 fuse_dax_read_iter+0x47/0x80 fuse_file_read_iter+0xae/0xd0 new_sync_read+0xfe/0x180 ? 0xffffffff81000000 vfs_read+0x14d/0x1a0 ksys_read+0x6d/0xf0 __x64_sys_read+0x1a/0x20 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The tail command will call read() with a count of 0. In this case, iomap_iter() will report this WARNING, and always return 1 which casuing the infinite loop in dax_iomap_rw(). Fixing by checking count whether is 0 in dax_iomap_rw().
AI-Powered Analysis
Technical Analysis
CVE-2022-48635 is a medium-severity vulnerability in the Linux kernel affecting the fsdax subsystem, specifically in the dax_iomap_rw() function. The flaw manifests as an infinite loop triggered when the read() system call is invoked with a count of zero, such as when using the 'tail' command on virtiofs. Internally, iomap_iter() incorrectly returns 1 when the count is zero, causing dax_iomap_rw() to loop indefinitely. This results in a CPU warning and potential resource exhaustion. The vulnerability stems from improper handling of zero-length reads in the dax_iomap_rw() function, violating expected iteration behavior. The fix involves adding a check to handle zero count values correctly, preventing the infinite loop. The vulnerability is classified under CWE-835 (Loop with Unreachable Exit Condition) and has a CVSS 3.1 base score of 6.2, indicating a medium severity with local attack vector, low complexity, no privileges required, no user interaction, unchanged scope, and impact limited to availability (denial of service). No known exploits are currently reported in the wild. The affected Linux kernel versions include the commit identified by ca289e0b95afa973d204c77a4ad5c37e06145fbf and likely other versions prior to the patch. This vulnerability primarily impacts systems using the fsdax and virtiofs features, which are relevant in environments leveraging persistent memory and virtualized file systems, respectively.
Potential Impact
For European organizations, the impact of CVE-2022-48635 centers on potential denial-of-service conditions on Linux systems utilizing fsdax and virtiofs. Such systems are often found in data centers, cloud infrastructure, and virtualization platforms that employ persistent memory technologies or advanced file system features. An infinite loop in kernel space can lead to CPU resource exhaustion, degraded system performance, or crashes, potentially disrupting critical services. While the vulnerability does not compromise confidentiality or integrity, availability impacts could affect high-availability environments, financial services, telecommunications, and public sector infrastructure relying on Linux-based virtualization. The local attack vector and absence of required privileges limit exploitation to users or processes with local access, reducing remote attack risks but increasing concerns in multi-tenant or shared environments. European organizations with virtualized workloads or persistent memory deployments should assess exposure, as denial-of-service conditions could lead to operational downtime and associated financial or reputational damage.
Mitigation Recommendations
To mitigate CVE-2022-48635, European organizations should: 1) Apply the latest Linux kernel patches that include the fix for the infinite loop in dax_iomap_rw(), ensuring kernel versions are updated beyond the commit ca289e0b95afa973d204c77a4ad5c37e06145fbf. 2) Audit systems for usage of fsdax and virtiofs features, particularly in virtualized or persistent memory environments, to identify potentially vulnerable hosts. 3) Limit local user access to trusted personnel and processes, as exploitation requires local interaction with the read() syscall on affected filesystems. 4) Implement monitoring for unusual CPU usage or kernel warnings related to iomap_iter or dax_iomap_rw to detect potential exploitation attempts or system instability. 5) In environments where immediate patching is not feasible, consider disabling fsdax or virtiofs features if not critical to operations, to reduce attack surface. 6) Incorporate this vulnerability into incident response and vulnerability management workflows to ensure timely detection and remediation.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-25T13:44:28.315Z
- Cisa Enriched
- true
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 682d982ec4522896dcbe5d2d
Added to database: 5/21/2025, 9:09:02 AM
Last enriched: 6/30/2025, 5:56:10 PM
Last updated: 7/25/2025, 11:11:07 AM
Views: 11
Related Threats
CVE-2025-8818: OS Command Injection in Linksys RE6250
MediumCVE-2025-8816: Stack-based Buffer Overflow in Linksys RE6250
HighCVE-2025-8815: Path Traversal in 猫宁i Morning
MediumCVE-2025-8814: Cross-Site Request Forgery in atjiu pybbs
MediumCVE-2025-8813: Open Redirect in atjiu pybbs
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.