Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-48697

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a use-after-free Fix the following use-after-free complaint triggered by blktests nvme/004: BUG: KASAN: user-memory…

Published May 3, 2024CWE-416EPSS 0.59%

Overview

CVE-2022-48697 is a critical-severity vulnerability. It was published on May 3, 2024 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

nvmet: fix a use-after-free

Fix the following use-after-free complaint triggered by blktests nvme/004:

BUG: KASAN: user-memory-access in blk_mq_complete_request_remote+0xac/0x350

Read of size 4 at addr 0000607bd1835943 by task kworker/13:1/460

Workqueue: nvmet-wq nvme_loop_execute_work [nvme_loop]

Call Trace:

show_stack+0x52/0x58

dump_stack_lvl+0x49/0x5e

print_report.cold+0x36/0x1e2

kasan_report+0xb9/0xf0

__asan_load4+0x6b/0x80

blk_mq_complete_request_remote+0xac/0x350

nvme_loop_queue_response+0x1df/0x275 [nvme_loop]

__nvmet_req_complete+0x132/0x4f0 [nvmet]

nvmet_req_complete+0x15/0x40 [nvmet]

nvmet_execute_io_connect+0x18a/0x1f0 [nvmet]

nvme_loop_execute_work+0x20/0x30 [nvme_loop]

process_one_work+0x56e/0xa70

worker_thread+0x2d1/0x640

kthread+0x183/0x1c0

ret_from_fork+0x1f/0x30

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/17f121ca3ec6be0fb32d77c7f65362934a38cc8eRefgit.kernel.org/stable/c/4484ce97a78171668c402e0c45db7f760aea8060Refgit.kernel.org/stable/c/6a02a61e81c231cc5c680c5dbf8665275147ac52Refgit.kernel.org/stable/c/8d66989b5f7bb28bba2f8e1e2ffc8bfef4a10717Refgit.kernel.org/stable/c/be01f1c988757b95f11f090a9f491365670a522bRefgit.kernel.org/stable/c/ebf46da50beb78066674354ad650606a467e33faRefgit.kernel.org/stable/c/17f121ca3ec6be0fb32d77c7f65362934a38cc8eRefgit.kernel.org/stable/c/4484ce97a78171668c402e0c45db7f760aea8060Refgit.kernel.org/stable/c/6a02a61e81c231cc5c680c5dbf8665275147ac52Refgit.kernel.org/stable/c/8d66989b5f7bb28bba2f8e1e2ffc8bfef4a10717

How CyberStrike helps

Frequently asked questions

What is CVE-2022-48697?

CVE-2022-48697 is a critical-severity vulnerability. It was published on May 3, 2024 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2022-48697?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

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

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

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-48697 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 CRITICAL CVEs from 2022

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999