CVE-2022-49395: um: Fix out-of-bounds read in LDT setup
In the Linux kernel, the following vulnerability has been resolved:
um: Fix out-of-bounds read in LDT setup
syscall_stub_data() expects the data_count parameter to be the number of
longs, not bytes.
==================================================================
BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0
Read of size 128 at addr 000000006411f6f0 by task swapper/1
CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18
Call Trace:
show_stack.cold+0x166/0x2a7
__dump_stack+0x3a/0x43
dump_stack_lvl+0x1f/0x27
print_report.cold+0xdb/0xf81
kasan_report+0x119/0x1f0
kasan_check_range+0x3a3/0x440
memcpy+0x52/0x140
syscall_stub_data+0x70/0xe0
write_ldt_entry+0xac/0x190
init_new_ldt+0x515/0x960
init_new_context+0x2c4/0x4d0
mm_init.constprop.0+0x5ed/0x760
mm_alloc+0x118/0x170
0x60033f48
do_one_initcall+0x1d7/0x860
0x60003e7b
kernel_init+0x6e/0x3d4
new_thread_handler+0x1e7/0x2c0
The buggy address belongs to stack of task swapper/1
and is located at offset 64 in frame:
init_new_ldt+0x0/0x960
This frame has 2 objects:
[32, 40) 'addr'
[64, 80) 'desc'
==================================================================
Security readout for executives and security teams
Plain-English summary
CVE-2022-49395 is a Linux kernel out-of-bounds read in the User-Mode Linux LDT setup path. A local low-privileged user may trigger memory disclosure or a crash. The source bundle lists high severity with confidentiality and availability impact, but no evidence of active exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue, especially for multi-user Linux, shared hosting, CI, research, or sandbox environments. It is not currently supported as internet-exploited, but kernel memory exposure and crash potential justify timely patching.
Technical view
The bug is in Linux kernel um LDT setup: syscall_stub_data() was given a byte count where it expected a count of longs, causing a stack out-of-bounds read detected by KASAN. The CVSS vector is local, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.
Likely exposure
Exposure is most likely on systems running affected Linux kernel versions or builds using the User-Mode Linux architecture path. The provided affected data lists multiple stable branches and upstream commits, but it does not identify specific distributions or appliances.
Exploitation context
The CVSS vector indicates local exploitation requiring low privileges. The CVE is not marked in KEV, and the provided sources do not cite public exploitation. No remote attack path is supported by the source bundle.
Researcher notes
The source evidence is kernel-level and commit-focused. Validate branch ancestry carefully because the affected version list includes stable-branch and commit identifiers but no distribution mapping. Do not assume exploitability outside the User-Mode Linux LDT setup path without confirming code reachability.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Check distribution advisories for fixed package versions.
Prioritize systems allowing local untrusted users or UML workloads.
Restrict local shell access until patched where feasible.
Validation and detection
Inventory Linux kernel versions across affected assets.
Identify systems using User-Mode Linux or custom kernel builds.
Confirm deployed kernels include one of the referenced stable commits.
Review vulnerability scanner results against vendor advisory fixed versions.
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.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.