CVE-2024-26901

do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak

MEDIUM
5.5
CVSS Score
Published: April 17, 2024 at 10:27 AM UTC
Updated: October 15, 2026 at 01:17 AM UTC
5 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.8%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak syzbot identified a kernel information leak vulnerability in do_sys_name_to_handle() and issued the following report [1]. [1] "BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline] BUG: KMSAN: kernel-infoleak in _copy_to_user+0xbc/0x100 lib/usercopy.c:40 instrument_copy_to_user include/linux/instrumented.h:114 [inline] _copy_to_user+0xbc/0x100 lib/usercopy.c:40 copy_to_user include/linux/uaccess.h:191 [inline] do_sys_name_to_handle fs/fhandle.c:73 [inline] __do_sys_name_to_handle_at fs/fhandle.c:112 [inline] __se_sys_name_to_handle_at+0x949/0xb10 fs/fhandle.c:94 __x64_sys_name_to_handle_at+0xe4/0x140 fs/fhandle.c:94 ... Uninit was created at: slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768 slab_alloc_node mm/slub.c:3478 [inline] __kmem_cache_alloc_node+0x5c9/0x970 mm/slub.c:3517 __do_kmalloc_node mm/slab_common.c:1006 [inline] __kmalloc+0x121/0x3c0 mm/slab_common.c:1020 kmalloc include/linux/slab.h:604 [inline] do_sys_name_to_handle fs/fhandle.c:39 [inline] __do_sys_name_to_handle_at fs/fhandle.c:112 [inline] __se_sys_name_to_handle_at+0x441/0xb10 fs/fhandle.c:94 __x64_sys_name_to_handle_at+0xe4/0x140 fs/fhandle.c:94 ... Bytes 18-19 of 20 are uninitialized Memory access of size 20 starts at ffff888128a46380 Data copied to user address 0000000020000240" Per Chuck Lever's suggestion, use kzalloc() instead of kmalloc() to solve the problem.

Affected

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

2.6.39 ≤ v < 4.19.3114.20 ≤ v < 5.4.2735.11 ≤ v < 5.15.1535.16 ≤ v < 6.1.835.5 ≤ v < 5.10.2146.2 ≤ v < 6.6.236.7 ≤ v < 6.7.116.8 ≤ v < 6.8.22.6.39990d6c2d7aee921e3bce22b2d6a750fd552262be
Vendor states this is fixed in 3948abaa4e2be938ccdfc289385a27342fb13d43 (fixed)
Vendor states this is fixed in 423b6bdf19bbc5e1f7e7461045099917378f7e71 (fixed)
Vendor states this is fixed in 4bac28f441e3cc9d3f1a84c8d023228a68d8a7c1 (fixed)
Vendor states this is fixed in 772a7def9868091da3bcb0d6c6ff9f0c03d7fa8b (fixed)
Vendor states this is fixed in bf9ec1b24ab4e94345aa1c60811dd329f069c38b (fixed)
Vendor states this is fixed in c1362eae861db28b1608b9dc23e49634fe87b63b (fixed)
Vendor states this is fixed in cba138f1ef37ec6f961baeab62f312dedc7cf730 (fixed)
Vendor states this is fixed in cde76b3af247f615447bcfecf610bb76c3529126 (fixed)
Vendor states this is fixed in e6450d5e46a737a008b4885aa223486113bf0ad6 (fixed)
Vendor states this is fixed in 2.6.39 (unaffected)
Vendor states this is fixed in 4.19.311 (unaffected)
Vendor states this is fixed in 5.10.214 (unaffected)
Vendor states this is fixed in 5.15.153 (unaffected)
Vendor states this is fixed in 5.4.273 (unaffected)
Vendor states this is fixed in 6.1.83 (unaffected)
Vendor states this is fixed in 6.6.23 (unaffected)
Vendor states this is fixed in 6.7.11 (unaffected)
Vendor states this is fixed in 6.8.2 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement
V3.1.0 ≤ v < V3.1.53.1.0
Affected range stops below V3.1.5, so it looks safe — our inference, not a vendor statement

References (13)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3948abaa4e2be938ccdfc289385a27342fb13d43
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/423b6bdf19bbc5e1f7e7461045099917378f7e71
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4bac28f441e3cc9d3f1a84c8d023228a68d8a7c1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/772a7def9868091da3bcb0d6c6ff9f0c03d7fa8b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bf9ec1b24ab4e94345aa1c60811dd329f069c38b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c1362eae861db28b1608b9dc23e49634fe87b63b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cba138f1ef37ec6f961baeab62f312dedc7cf730
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cde76b3af247f615447bcfecf610bb76c3529126

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card