CVE-2022-49505
published 2025-02-26CVE-2022-49505: 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…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.28%
19.8th percentile
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]
[ 68.760756] dump_stack_lvl+0x57/0x7d
[ 68.760756] print_report.cold+0x5e/0x5db
[ 68.760756] ? __lock_acquire+0x3ec1/0x6750
[ 68.760756] kasan_report+0xbe/0x1c0
[ 68.760756] ? __lock_acquire+0x3ec1/0x6750
[ 68.760756] __lock_acquire+0x3ec1/0x6750
[ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410
[ 68.760756] ? register_lock_class+0x18d0/0x18d0
[ 68.760756] lock_acquire+0x1ac/0x4f0
[ 68.760756] ? rfkill_blocked+0xe/0x60
[ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410
[ 68.760756] ? mutex_lock_io_nested+0x12c0/0x12c0
[ 68.760756] ? nla_get_range_signed+0x540/0x540
[ 68.760756] ? _raw_spin_lock_irqsave+0x4e/0x50
[ 68.760756] _raw_spin_lock_irqsave+0x39/0x50
[ 68.760756] ? rfkill_blocked+0xe/0x60
[ 68.760756] rfkill_blocked+0xe/0x60
[ 68.760756] nfc_dev_up+0x84/0x260
[ 68.760756] nfc_genl_dev_up+0x90/0xe0
[ 68.760756] genl_family_rcv_msg_doit+0x1f4/0x2f0
[ 68.760756] ? genl_family_rcv_msg_attrs_parse.constprop.0+0x230/0x230
[ 68.760756] ? security_capable+0x51/0x90
[ 68.760756] genl_rcv_msg+0x280/0x5
Affected
32 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 307d2e6cebfca9d92f86c8e2c8e3dd4a8be46ba6 < fbf9c4c714d3cdeb98b6a18e4d057f931cad1d81 | fbf9c4c714d3cdeb98b6a18e4d057f931cad1d81 |
| linux | linux | >= 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 < 4a68938f43b7c2663e4c90bb9bbe29ac8b9a42a0 | 4a68938f43b7c2663e4c90bb9bbe29ac8b9a42a0 |
| linux | linux | >= 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 < 4f5d71930f41be78557f9714393179025baacd65 | 4f5d71930f41be78557f9714393179025baacd65 |
| linux | linux | >= 3e3b5dfcd16a3e254aab61bd1e8c417dd4503102 < 1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9 | 1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9 |
| linux | linux | >= 4.14.256 < 4.14.283 | 4.14.283 |
| linux | linux | >= 4.19.218 < 4.19.247 | 4.19.247 |
| linux | linux | >= 4.4.293 < 4.5 | 4.5 |
| linux | linux | >= 4.9.291 < 4.9.318 | 4.9.318 |
| linux | linux | >= 47244ac0b65bd74cc70007d8e1bac68bd2baad19 < f81270125b50532624400063281e6611ecd61ddf | f81270125b50532624400063281e6611ecd61ddf |
| linux | linux | >= 5.10.82 < 5.10.121 | 5.10.121 |
| linux | linux | >= 5.15.5 < 5.15.46 | 5.15.46 |
| linux | linux | >= 5.4.162 < 5.4.198 | 5.4.198 |
| linux | linux | >= 73a0d12114b4bc1a9def79a623264754b9df698e < 2a1b5110c95e4d49c8c3906270dfcde680a5a7be | 2a1b5110c95e4d49c8c3906270dfcde680a5a7be |
| linux | linux | >= 8a9c61c3ef187d8891225f9b932390670a43a0d3 < 1632be63862f183cd5cf1cc094e698e6ec005dfd | 1632be63862f183cd5cf1cc094e698e6ec005dfd |
| linux | linux | >= c45cea83e13699bdfd47842e04d09dd43af4c371 < 6abfaca8711803d0d7cc8c0fac1070a88509d463 | 6abfaca8711803d0d7cc8c0fac1070a88509d463 |
| linux | linux | >= ff169909eac9e00bf1aa0af739ba6ddfb1b1d135 < a8e03bcad52dc9afabf650fdbad84f739cec9efa | a8e03bcad52dc9afabf650fdbad84f739cec9efa |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.14.256 < 4.14.283 | 4.14.283 |
| linux | linux_kernel | >= 4.19.218 < 4.19.247 | 4.19.247 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: NFC: NULL out the dev->rfkill to prevent UAF
vendor_redhat·2025-02-26·CVSS 7.8
CVE-2022-49505 [HIGH] CWE-416 kernel: NFC: NULL out the dev->rfkill to prevent UAF
kernel: NFC: NULL out the dev->rfkill to prevent UAF
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.7
Debian
CVE-2022-49505: linux - In the Linux kernel, the following vulnerability has been resolved: NFC: NULL o...
vendor_debian·2022·CVSS 7.8
CVE-2022-49505 [HIGH] CVE-2022-49505: linux - In the Linux kernel, the following vulnerability has been resolved: NFC: NULL o...
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-r
GHSA
GHSA-m645-2c8g-gg4p: In the Linux kernel, the following vulnerability has been resolved:
NFC: NULL out the dev->rfkill to prevent UAF
Commit 3e3b5dfcd16a ("NFC: reorder
ghsa_unreviewed·2025-02-27
CVE-2022-49505 [HIGH] CWE-416 GHSA-m645-2c8g-gg4p: In the Linux kernel, the following vulnerability has been resolved:
NFC: NULL out the dev->rfkill to prevent UAF
Commit 3e3b5dfcd16a ("NFC: reorder
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
OSV
CVE-2022-49505: In the Linux kernel, the following vulnerability has been resolved: NFC: NULL out the dev->rfkill to prevent UAF Commit 3e3b5dfcd16a ("NFC: reorder th
osv·2025-02-26·CVSS 7.8
CVE-2022-49505 [HIGH] CVE-2022-49505: In the Linux kernel, the following vulnerability has been resolved: NFC: NULL out the dev->rfkill to prevent UAF Commit 3e3b5dfcd16a ("NFC: reorder th
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-r
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1632be63862f183cd5cf1cc094e698e6ec005dfdhttps://git.kernel.org/stable/c/1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9https://git.kernel.org/stable/c/2a1b5110c95e4d49c8c3906270dfcde680a5a7behttps://git.kernel.org/stable/c/4a68938f43b7c2663e4c90bb9bbe29ac8b9a42a0https://git.kernel.org/stable/c/4f5d71930f41be78557f9714393179025baacd65https://git.kernel.org/stable/c/6abfaca8711803d0d7cc8c0fac1070a88509d463https://git.kernel.org/stable/c/a8e03bcad52dc9afabf650fdbad84f739cec9efahttps://git.kernel.org/stable/c/f81270125b50532624400063281e6611ecd61ddfhttps://git.kernel.org/stable/c/fbf9c4c714d3cdeb98b6a18e4d057f931cad1d81
2025-02-26
Published