LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50699: selinux: enable use of both GFP_KERNEL and GFP_ATOMIC in convert_context()

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]

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects SELinux handling during security context conversion. Under certain conditions, the kernel may try to sleep while in an atomic locked section, producing a kernel warning and potentially affecting system stability. The sources do not provide CVSS, confirmed impact, or evidence of active exploitation.

Executive priority

Treat as a kernel maintenance item, not an emergency based on current evidence. Prioritize patching on SELinux-dependent servers or regulated workloads where kernel stability and access-control reliability are business-critical.

Technical view

In SELinux sidtab_context_to_sid(), convert_context() could allocate memory with GFP_KERNEL while protected by spin_lock_irqsave(), causing a sleep-in-atomic-context warning. The kernel fix adds a gfp_t parameter so callers use GFP_ATOMIC or GFP_KERNEL appropriately.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with SELinux in use. The source lists Linux kernel 5.x and 6.x affected ranges, but distribution backports may change exposure and must be checked with vendor advisories.

Exploitation context

No source in the bundle reports active exploitation, weaponized code, or remote attack conditions. The described trigger occurred during normal filesystem lookup/stat activity involving SELinux labels and SID table conversion.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. No CVSS, CWE, exploitability assessment, or downstream vendor mapping is provided. Validate affectedness by kernel branch, vendor backport status, SELinux usage, and presence of the specific fix commits.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable Linux fixes.
  • Prioritize SELinux-enabled systems on affected kernel branches.
  • If no update is available, request distribution or vendor guidance.
  • Reboot into the fixed kernel after approved maintenance.

Validation and detection

  • Inventory Linux hosts and their running kernel versions.
  • Identify systems with SELinux enabled or deployed.
  • Check vendor advisories for backports of the referenced commits.
  • Review kernel logs for sleep-in-atomic-context SELinux warnings.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50699 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxee1a84fdfeedfd7362e9a8a8f15fedc3482ade2d, ee1a84fdfeedfd7362e9a8a8f15fedc3482ade2d, ee1a84fdfeedfd7362e9a8a8f15fedc3482ade2d, ee1a84fdfeedfd7362e9a8a8f15fedc3482ade2dunaffected
LinuxLinux5.0, 0, 5.10.152, 5.15.76, 6.0.6, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.