Menu

Star on GitHub · 3.4k

CVE-2022-48853

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: swiotlb: fix info leak with DMA_FROM_DEVICE The problem I'm addressing was discovered by the LTP test covering cve-2018-1000204.

Published Jul 16, 2024EPSS 0.27%

Overview

CVE-2022-48853 is a medium-severity vulnerability. It was published on July 16, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

swiotlb: fix info leak with DMA_FROM_DEVICE

The problem I'm addressing was discovered by the LTP test covering

cve-2018-1000204.

A short description of what happens follows:

1) The test case issues a command code 00 (TEST UNIT READY) via the SG_IO

interface with: dxfer_len == 524288, dxdfer_dir == SG_DXFER_FROM_DEV

and a corresponding dxferp. The peculiar thing about this is that TUR

is not reading from the device.

2) In sg_start_req() the invocation of blk_rq_map_user() effectively

bounces the user-space buffer. As if the device was to transfer into

it. Since commit a45b599ad808 ("scsi: sg: allocate with __GFP_ZERO in

sg_build_indirect()") we make sure this first bounce buffer is

allocated with GFP_ZERO.

3) For the rest of the story we keep ignoring that we have a TUR, so the

device won't touch the buffer we prepare as if the we had a

DMA_FROM_DEVICE type of situation. My setup uses a vir

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.

Frequently asked questions

What is CVE-2022-48853?

CVE-2022-48853 is a medium-severity vulnerability. It was published on July 16, 2024 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2022-48853?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

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-48853?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-48853 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
Watch the demo →