CVE-2022-50779

orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string()

N/A
Published: December 24, 2025 at 01:06 PM UTC
Updated: June 17, 2026 at 05:24 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
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: orangefs: Fix kmemleak in orangefs_prepare_debugfs_help_string() When insert and remove the orangefs module, then debug_help_string will be leaked: unreferenced object 0xffff8881652ba000 (size 4096): comm "insmod", pid 1701, jiffies 4294893639 (age 13218.530s) hex dump (first 32 bytes): 43 6c 69 65 6e 74 20 44 65 62 75 67 20 4b 65 79 Client Debug Key 77 6f 72 64 73 20 61 72 65 20 75 6e 6b 6e 6f 77 words are unknow backtrace: [<0000000004e6f8e3>] kmalloc_trace+0x27/0xa0 [<0000000006f75d85>] orangefs_prepare_debugfs_help_string+0x5e/0x480 [orangefs] [<0000000091270a2a>] _sub_I_65535_1+0x57/0xf70 [crc_itu_t] [<000000004b1ee1a3>] do_one_initcall+0x87/0x2a0 [<000000001d0614ae>] do_init_module+0xdf/0x320 [<00000000efef068c>] load_module+0x2f98/0x3330 [<000000006533b44d>] __do_sys_finit_module+0x113/0x1b0 [<00000000a0da6f99>] do_syscall_64+0x35/0x80 [<000000007790b19b>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 When remove the module, should always free debug_help_string. Should always free the allocated buffer when change the free_debug_help_string.

Affected

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

4.9 ≤ v < 4.14.3034.9 ≤ v < 4.19.2704.9 ≤ v < 4.9.3374.9 ≤ v < 5.10.1634.9 ≤ v < 5.15.864.9 ≤ v < 5.4.2294.9 ≤ v < 6.0.164.9 ≤ v < 6.1.24.9 ≤ v < 6.24.9dc0336214eb07ee9de2a41dd4c81c744ffa419ac
Vendor states this is fixed in 19be31668552a198e887762e25bdcc560800ecb4 (fixed)
Vendor states this is fixed in 2e7c09121064df93c58bbc49d3d0f608d3f584bd (fixed)
Vendor states this is fixed in 39529b79b023713d4f2d3479dc0ca43ba99df726 (fixed)
Vendor states this is fixed in 3fc221d9a16339a913a0341d3efc7fef339073e1 (fixed)
Vendor states this is fixed in 44d3eac26a5e5268d11cc342dc202b0d31505c0a (fixed)
Vendor states this is fixed in b8affa0c6405ee968dcb6030bee2cf719a464752 (fixed)
Vendor states this is fixed in ba9d3b9cec20957fd86bb1bf525b4ea8b64b2dea (fixed)
Vendor states this is fixed in d23417a5bf3a3afc55de5442eb46e1e60458b0a1 (fixed)
Vendor states this is fixed in f2b8a6aac561a49fe02c99683c40a8b87a9f68fc (fixed)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.86 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.16 (unaffected)
Vendor states this is fixed in 6.1.2 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (9)

Quick Info

StatusDEFERRED

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