CVE-2022-49395

um: Fix out-of-bounds read in LDT setup

HIGH

7.1

CVSS Score

Published: February 26, 2025 at 02:11 AM UTC

Updated: June 17, 2026 at 05:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.1

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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' ==================================================================

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.15 ≤ v < 4.14.2832.6.15 ≤ v < 4.19.2472.6.15 ≤ v < 4.9.3182.6.15 ≤ v < 5.10.1212.6.15 ≤ v < 5.15.462.6.15 ≤ v < 5.17.142.6.15 ≤ v < 5.18.32.6.15 ≤ v < 5.192.6.15 ≤ v < 5.4.1984.10 ≤ v < 4.14.2834.15 ≤ v < 4.19.2474.20 ≤ v < 5.4.1985.11 ≤ v < 5.15.465.16 ≤ v < 5.17.145.18 ≤ v < 5.18.35.5 ≤ v < 5.10.1212.6.15858259cf7d1c443c836a2022b78cb281f0a9b95e

Vendor states this is fixed in 10995a382271254bd276627ec74136da4a23c4a6 (fixed)

Vendor states this is fixed in 24ca648bf5f72ed8878cf09b5d4431935779681e (fixed)

Vendor states this is fixed in 2a4a62a14be1947fa945c5c11ebf67326381a568 (fixed)

Vendor states this is fixed in 3549ab4b962cf619e8c55484a0d870a34b3f845f (fixed)

Vendor states this is fixed in 668ca34a428d6ffc0f99a1a6a9b661a288d4183b (fixed)

Vendor states this is fixed in 91e5ba2af2d729d5126aefd5aa3eadc69b8426e5 (fixed)

Vendor states this is fixed in 9caad70819aef3431abaf73ba5163b55b161aba0 (fixed)

Vendor states this is fixed in cf0dabc37446c5ee538ae7b4c467ab0e53fa5463 (fixed)

Vendor states this is fixed in ef1dc929a1e5fa1b2d842256db9fb8710d3be910 (fixed)

Vendor states this is fixed in 2.6.15 (unaffected)

Vendor states this is fixed in 4.14.283 (unaffected)

Vendor states this is fixed in 4.19.247 (unaffected)

Vendor states this is fixed in 4.9.318 (unaffected)

Vendor states this is fixed in 5.10.121 (unaffected)

Vendor states this is fixed in 5.15.46 (unaffected)

Vendor states this is fixed in 5.17.14 (unaffected)

Vendor states this is fixed in 5.18.3 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)

Vendor states this is fixed in 5.4.198 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references