CVE-2022-49505

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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/0x500 [ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 [ 68.760756] ? lock_acquire+0x1ac/0x4f0 [ 68.760756] ? nfc_genl_dev_down+0xe0/0xe0 [ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 [ 68.760756] netlink_rcv_skb+0x11b/0x340 [ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 [ 68.760756] ? netlink_ack+0x9c0/0x9c0 [ 68.760756] ? netlink_deliver_tap+0x136/0xb00 [ 68.760756] genl_rcv+0x1f/0x30 [ 68.760756] netlink_unicast+0x430/0x710 [ 68.760756] ? memset+0x20/0x40 [ 68.760756] ? netlink_attachskb+0x740/0x740 [ 68.760756] ? __build_skb_around+0x1f4/0x2a0 [ 68.760756] netlink_sendmsg+0x75d/0xc00 [ 68.760756] ? netlink_unicast+0x710/0x710 [ 68.760756] ? netlink_unicast+0x710/0x710 [ 68.760756] sock_sendmsg+0xdf/0x110 [ 68.760756] __sys_sendto+0x19e/0x270 [ 68.760756] ? __ia32_sys_getpeername+0xa0/0xa0 [ 68.760756] ? fd_install+0x178/0x4c0 [ 68.760756] ? fd_install+0x195/0x4c0 [ 68.760756] ? kernel_fpu_begin_mask+0x1c0/0x1c0 [ 68.760756] __x64_sys_sendto+0xd8/0x1b0 [ 68.760756] ? lockdep_hardirqs_on+0xbf/0x130 [ 68.760756] ? syscall_enter_from_user_mode+0x1d/0x50 [ 68.760756] do_syscall_64+0x3b/0x90 [ 68.760756] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 68.760756] RIP: 0033:0x7f67fb50e6b3 ... [ 68.760756] RSP: 002b:00007f67fa91fe90 EFLAGS: 00000293 ORIG_RAX: 000000000000002c [ 68.760756] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f67fb50e6b3 [ 68.760756] RDX: 000000000000001c RSI: 0000559354603090 RDI: 0000000000000003 [ 68.760756] RBP: 00007f67fa91ff00 R08: 00007f67fa91fedc R09: 000000000000000c [ 68.760756] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffe824d496e [ 68.760756] R13: 00007ffe824d496f R14: 00007f67fa120000 R15: 0000000000000003

[ 68.760756] [ 68.760756] [ 68.760756] Allocated by task 279: [ 68.760756] kasan_save_stack+0x1e/0x40 [ ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f5d71930f41be78557f9714393179025baacd65
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a68938f43b7c2663e4c90bb9bbe29ac8b9a42a0
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1632be63862f183cd5cf1cc094e698e6ec005dfd
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a1b5110c95e4d49c8c3906270dfcde680a5a7be
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fbf9c4c714d3cdeb98b6a18e4d057f931cad1d81
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6abfaca8711803d0d7cc8c0fac1070a88509d463
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f81270125b50532624400063281e6611ecd61ddf
generic

NFC: NULL out the dev->rfkill to prevent UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a8e03bcad52dc9afabf650fdbad84f739cec9efa

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.318—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (14 versions)5.10.127-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.18.5-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-09-20 20:13 UTCEPSS rescore
  2. 2026-09-16 14:05 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-15 03:07 UTCEPSS rescore
  5. 2026-09-13 16:44 UTCEPSS rescore
  6. 2026-09-11 14:50 UTCEPSS rescore
  7. 2026-09-11 09:34 UTCEPSS rescore
  8. 2026-09-08 21:57 UTCEPSS rescore
  9. 2026-09-07 15:59 UTCEPSS rescore
  10. 2026-09-07 04:48 UTCOSV refresh
  11. 2026-09-06 13:45 UTCEPSS rescore
  12. 2026-09-05 15:25 UTCEPSS rescore
  13. 2026-09-04 13:57 UTCEPSS rescore
  14. 2026-09-04 05:04 UTCEPSS rescore
  15. 2026-09-02 14:09 UTCEPSS rescore
  16. 2026-09-01 13:51 UTCEPSS rescore
  17. 2026-08-30 19:15 UTCEPSS rescore
  18. 2026-08-30 01:19 UTCEPSS rescore
  19. 2026-08-28 21:38 UTCEPSS rescore
  20. 2026-08-27 14:22 UTCEPSS rescore
  21. 2026-08-26 14:43 UTCEPSS rescore
  22. 2026-08-25 13:46 UTCEPSS rescore
  23. 2026-08-23 00:17 UTCEPSS rescore
  24. 2026-08-21 23:46 UTCEPSS rescore
  25. 2026-08-20 22:53 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 14:31 UTCOSV refresh
  2. 2026-08-19 17:01 UTCEPSS rescore
  3. 2026-08-18 13:45 UTCEPSS rescore
  4. 2026-08-17 13:44 UTCEPSS rescore
  5. 2026-08-16 14:53 UTCEPSS rescore
  6. 2026-08-16 02:12 UTCEPSS rescore
  7. 2026-08-15 01:27 UTCEPSS rescore
  8. 2026-08-13 21:58 UTCEPSS rescore
  9. 2026-08-12 13:48 UTCEPSS rescore
  10. 2026-08-09 13:44 UTCEPSS rescore
  11. 2026-08-09 13:44 UTCEPSS rescore
  12. 2026-08-08 16:34 UTCEPSS rescore
  13. 2026-08-07 16:24 UTCEPSS rescore
  14. 2026-08-06 13:44 UTCEPSS rescore
  15. 2026-08-05 19:15 UTCEPSS rescore
  16. 2026-08-05 09:31 UTCEG score recompute
  17. 2026-08-05 09:31 UTCGHSA enrichment
  18. 2026-08-04 15:07 UTCEPSS rescore
  19. 2026-08-04 10:35 UTCEPSS rescore
  20. 2026-08-04 09:46 UTCEG score recompute
  21. 2026-08-04 09:46 UTCGHSA enrichment
  22. 2026-08-03 10:33 UTCEPSS rescore
  23. 2026-08-02 02:24 UTCEPSS rescore
  24. 2026-08-01 04:13 UTCEPSS rescore
  25. 2026-08-01 04:13 UTCEPSS rescore
  26. 2026-07-30 16:25 UTCEPSS rescore
  27. 2026-07-30 01:28 UTCEPSS rescore
  28. 2026-07-28 15:34 UTCEPSS rescore
  29. 2026-07-26 14:52 UTCEPSS rescore
  30. 2026-07-26 14:52 UTCEPSS rescore
  31. 2026-07-25 14:16 UTCEPSS rescore
  32. 2026-07-24 14:15 UTCEPSS rescore
  33. 2026-07-24 13:41 UTCOSV refresh
  34. 2026-07-23 14:16 UTCEPSS rescore
  35. 2026-07-23 14:16 UTCEPSS rescore
  36. 2026-07-23 02:16 UTCEG score recompute
  37. 2026-07-22 23:04 UTCEG score recompute
  38. 2026-07-22 14:06 UTCEPSS rescore
  39. 2026-07-22 14:06 UTCEPSS rescore
  40. 2026-07-21 15:23 UTCEPSS rescore
  41. 2026-07-21 15:23 UTCEPSS rescore
  42. 2026-07-20 17:05 UTCEPSS rescore
  43. 2026-07-19 14:29 UTCEPSS rescore
  44. 2026-07-19 14:29 UTCEPSS rescore
  45. 2026-07-19 02:27 UTCEPSS rescore
  46. 2026-07-19 02:27 UTCEPSS rescore
  47. 2026-07-18 10:03 UTCEPSS rescore
  48. 2026-07-18 10:03 UTCEPSS rescore
  49. 2026-07-16 17:00 UTCEPSS rescore
  50. 2026-07-15 16:56 UTCEPSS rescore
  51. 2026-07-15 16:56 UTCEPSS rescore
  52. 2026-07-15 01:58 UTCEPSS rescore
  53. 2026-07-15 01:58 UTCEPSS rescore
  54. 2026-07-13 22:28 UTCEPSS rescore
  55. 2026-07-13 22:28 UTCEPSS rescore
  56. 2026-07-13 06:11 UTCEPSS rescore
  57. 2026-07-13 06:11 UTCEPSS rescore
  58. 2026-07-12 05:44 UTCEPSS rescore
  59. 2026-07-11 08:25 UTCEPSS rescore
  60. 2026-07-11 08:25 UTCEPSS rescore
  61. 2026-07-09 19:08 UTCEPSS rescore
  62. 2026-07-08 15:13 UTCEPSS rescore
  63. 2026-07-07 13:44 UTCEPSS rescore
  64. 2026-07-07 09:21 UTCOSV refresh
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 02:21 UTCEPSS rescore
  67. 2026-07-05 02:28 UTCEPSS rescore
  68. 2026-07-04 06:29 UTCEPSS rescore
  69. 2026-07-01 15:04 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-30 23:20 UTCEPSS rescore
  72. 2026-06-29 14:04 UTCEPSS rescore
  73. 2026-06-28 14:06 UTCEPSS rescore
  74. 2026-06-28 04:54 UTCEPSS rescore
  75. 2026-06-28 04:54 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-49505?
CVE-2022-49505 is a high vulnerability published on February 26, 2025. 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,}registerdevice") assumes the deviceisregistered() in function nfcdevup() will help to check when the rfkill is unregistered.…
When was CVE-2022-49505 disclosed?
CVE-2022-49505 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49505 actively exploited?
CVE-2022-49505 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2022-49505?
CVE-2022-49505 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49505?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49505, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49505

Explore →

Is Your Infrastructure Affected by CVE-2022-49505?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs