CVE-2022-49443

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2025-03-17. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

list: fix a data-race around ep->rdllist

ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to avoid store/load-tearing.

Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.

Commit bf3b9f6372c4 ("epoll: Add busy poll support to epoll with socket fds.") added the first lockless ep_events_available(), and commit c5a282e9635e ("fs/epoll: reduce the scope of wq lock in epoll_wait()") made some ep_events_available() calls lockless and added single call under a lock, finally commit e59d3c64cba6 ("epoll: eliminate unnecessary lock for zero timeout") made the last ep_events_available() lockless.

BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait

write to 0xffff88810480c7d8 of 8 bytes by task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff88810480c7d8 of 8 bytes by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40 fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281 [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80 fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0xffff88810480c7d0 -> 0xffff888103c15098

Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted: G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

February 26, 2025

Last Modified

October 1, 2025

Vendor Advisories for CVE-2022-49443(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 5.15.46osv

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 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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 141 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-49443?
CVE-2022-49443 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around ep->rdllist eppoll() first calls epevents_available() with no lock held and checks if ep->rdllist is empty by listemptycareful(), which reads rdllist->prev. Thus all accesses to it need some protection…
When was CVE-2022-49443 disclosed?
CVE-2022-49443 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49443 actively exploited?
CVE-2022-49443 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 92.4% of all scored CVEs.
What is the CVSS score of CVE-2022-49443?
CVE-2022-49443 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2022-49443?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49443, 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-49443

Explore →

Is Your Infrastructure Affected by CVE-2022-49443?

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