Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2022-49505

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: NFC: NULL out the dev->rfkill to prevent UAF Commit 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device") assumes…

Published Feb 26, 2025CWE-416EPSS 0.28%

Overview

CVE-2022-49505 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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:

NFC: NULL out the dev->rfkill to prevent UAF

Commit 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device")

assumes the device_is_registered() in function nfc_dev_up() will help

to check when the rfkill is unregistered. However, this check only

take effect when device_del(&dev->dev) is done in nfc_unregister_device().

Hence, the rfkill object is still possible be dereferenced.

The crash trace in latest kernel (5.18-rc2):

[ 68.760105] ==================================================================

[ 68.760330] BUG: KASAN: use-after-free in __lock_acquire+0x3ec1/0x6750

[ 68.760756] Read of size 8 at addr ffff888009c93018 by task fuzz/313

[ 68.760756]

[ 68.760756] CPU: 0 PID: 313 Comm: fuzz Not tainted 5.18.0-rc2 #4

[ 68.760756] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014

[ 68.760756] Call Trace:

[ 68.760756] <TASK>

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/1632be63862f183cd5cf1cc094e698e6ec005dfdRefgit.kernel.org/stable/c/1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9Refgit.kernel.org/stable/c/2a1b5110c95e4d49c8c3906270dfcde680a5a7beRefgit.kernel.org/stable/c/4a68938f43b7c2663e4c90bb9bbe29ac8b9a42a0Refgit.kernel.org/stable/c/4f5d71930f41be78557f9714393179025baacd65Refgit.kernel.org/stable/c/6abfaca8711803d0d7cc8c0fac1070a88509d463Refgit.kernel.org/stable/c/a8e03bcad52dc9afabf650fdbad84f739cec9efaRefgit.kernel.org/stable/c/f81270125b50532624400063281e6611ecd61ddfRefgit.kernel.org/stable/c/fbf9c4c714d3cdeb98b6a18e4d057f931cad1d81

How CyberStrike helps

Frequently asked questions

What is CVE-2022-49505?

CVE-2022-49505 is a high-severity vulnerability. It was published on February 26, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2022-49505?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. 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-49505?

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

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

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999