Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-48635

6.2 · MEDIUM

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.

Published Apr 28, 2024CWE-835EPSS 0.23%

Overview

CVE-2022-48635 is a medium-severity vulnerability. It was published on April 28, 2024 and has a CVSS 3.1 base score of 6.2 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical 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().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/17d9c15c9b9e7fb285f7ac5367dfb5f00ff575e3Refgit.kernel.org/stable/c/463f36137c40342fb03bba380c1bf703c40d89a6Refgit.kernel.org/stable/c/60644dffac87b1bb47bdb393aa29d5f2ffcf41a0Refgit.kernel.org/stable/c/929ef155e1da41c06f4d8ca86ae12b851a83a744Refgit.kernel.org/stable/c/17d9c15c9b9e7fb285f7ac5367dfb5f00ff575e3Refgit.kernel.org/stable/c/60644dffac87b1bb47bdb393aa29d5f2ffcf41a0Refgit.kernel.org/stable/c/929ef155e1da41c06f4d8ca86ae12b851a83a744

How CyberStrike helps

Frequently asked questions

What is CVE-2022-48635?

CVE-2022-48635 is a medium-severity vulnerability. It was published on April 28, 2024 and has a CVSS 3.1 base score of 6.2 (MEDIUM).

How severe is CVE-2022-48635?

This vulnerability has a CVSS 3.1 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2022-48635?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-48635?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-48635 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999