CVE-2022-50699

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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

selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()

The following warning was triggered on a hardware environment:

SELinux: Converting 162 SID table entries... BUG: sleeping function called from invalid context at __might_sleep+0x60/0x74 0x0 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 5943, name: tar CPU: 7 PID: 5943 Comm: tar Tainted: P O 5.10.0 #1 Call trace: dump_backtrace+0x0/0x1c8 show_stack+0x18/0x28 dump_stack+0xe8/0x15c ___might_sleep+0x168/0x17c __might_sleep+0x60/0x74 __kmalloc_track_caller+0xa0/0x7dc kstrdup+0x54/0xac convert_context+0x48/0x2e4 sidtab_context_to_sid+0x1c4/0x36c security_context_to_sid_core+0x168/0x238 security_context_to_sid_default+0x14/0x24 inode_doinit_use_xattr+0x164/0x1e4 inode_doinit_with_dentry+0x1c0/0x488 selinux_d_instantiate+0x20/0x34 security_d_instantiate+0x70/0xbc d_splice_alias+0x4c/0x3c0 ext4_lookup+0x1d8/0x200 [ext4] __lookup_slow+0x12c/0x1e4 walk_component+0x100/0x200 path_lookupat+0x88/0x118 filename_lookup+0x98/0x130 user_path_at_empty+0x48/0x60 vfs_statx+0x84/0x140 vfs_fstatat+0x20/0x30 __se_sys_newfstatat+0x30/0x74 __arm64_sys_newfstatat+0x1c/0x2c el0_svc_common.constprop.0+0x100/0x184 do_el0_svc+0x1c/0x2c el0_svc+0x20/0x34 el0_sync_handler+0x80/0x17c el0_sync+0x13c/0x140 SELinux: Context system_u:object_r:pssp_rsyslog_log_t:s0:c0 is not valid (left unmapped).

It was found that within a critical section of spin_lock_irqsave in sidtab_context_to_sid(), convert_context() (hooked by sidtab_convert_params.func) might cause the process to sleep via allocating memory with GFP_KERNEL, which is problematic.

As Ondrej pointed out [1], convert_context()/sidtab_convert_params.func has another caller sidtab_convert_tree(), which is okay with GFP_KERNEL. Therefore, fix this problem by adding a gfp_t argument for convert_context()/sidtab_convert_params.func and pass GFP_KERNEL/_ATOMIC properly in individual callers.

[PM: wrap long BUG() output lines, tweak subject line]

CVSS v3
—
EG Score
0.0(none)
EG Risk
—
EPSS
6.5%
KEV
Not listed

Published

December 24, 2025

Last Modified

April 15, 2026

References (4)

Vendor Advisories for CVE-2022-50699(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.10.152—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.

Data Freshness Timeline

(refreshed 13× in last 7d / 44× 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 131 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2022-50699?
CVE-2022-50699 is a none vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: selinux: enable use of both GFPKERNEL and GFPATOMIC in convert_context() The following warning was triggered on a hardware environment: SELinux: Converting 162 SID table entries... BUG: sleeping function called from invalid context…
When was CVE-2022-50699 disclosed?
CVE-2022-50699 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50699 actively exploited?
CVE-2022-50699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2022-50699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50699, 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

Explore the affected products and dependency analysis for CVE-2022-50699

Explore →

Is Your Infrastructure Affected by CVE-2022-50699?

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

Start Free Scan →Browse All CVEs