CVE-2022-49927

nfs4: Fix kmemleak when allocate slot failed

MEDIUM

5.5

CVSS Score

Published: May 1, 2025 at 02:11 PM UTC

Updated: June 17, 2026 at 05:19 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

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nfs4: Fix kmemleak when allocate slot failed If one of the slot allocate failed, should cleanup all the other allocated slots, otherwise, the allocated slots will leak: unreferenced object 0xffff8881115aa100 (size 64): comm ""mount.nfs"", pid 679, jiffies 4294744957 (age 115.037s) hex dump (first 32 bytes): 00 cc 19 73 81 88 ff ff 00 a0 5a 11 81 88 ff ff ...s......Z..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000007a4c434a>] nfs4_find_or_create_slot+0x8e/0x130 [<000000005472a39c>] nfs4_realloc_slot_table+0x23f/0x270 [<00000000cd8ca0eb>] nfs40_init_client+0x4a/0x90 [<00000000128486db>] nfs4_init_client+0xce/0x270 [<000000008d2cacad>] nfs4_set_client+0x1a2/0x2b0 [<000000000e593b52>] nfs4_create_server+0x300/0x5f0 [<00000000e4425dd2>] nfs4_try_get_tree+0x65/0x110 [<00000000d3a6176f>] vfs_get_tree+0x41/0xf0 [<0000000016b5ad4c>] path_mount+0x9b3/0xdd0 [<00000000494cae71>] __x64_sys_mount+0x190/0x1d0 [<000000005d56bdec>] do_syscall_64+0x35/0x80 [<00000000687c9ae4>] entry_SYSCALL_64_after_hwframe+0x46/0xb0

Affected

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

Linux Kernel · Linux

95%

3.12 ≤ v < 4.14.2993.12 ≤ v < 4.19.2653.12 ≤ v < 4.9.3333.12 ≤ v < 5.10.1543.12 ≤ v < 5.15.783.12 ≤ v < 5.4.2243.12 ≤ v < 6.0.83.12 ≤ v < 6.14.10 ≤ v < 4.14.2994.15 ≤ v < 4.19.2654.20 ≤ v < 5.4.2245.11 ≤ v < 5.15.785.16 ≤ v < 6.0.85.5 ≤ v < 5.10.1546.1 rc1 6.1 rc2 6.1 rc3abf79bb341bf52f75f295b850abdf5f78f584311

Vendor states this is fixed in 24641993a7dce6b1628645f4e1d97ca06c9f765d (fixed)

Vendor states this is fixed in 45aea4fbf61e205649c29200726b9f45c1718a67 (fixed)

Vendor states this is fixed in 7e8436728e22181c3f12a5dbabd35ed3a8b8c593 (fixed)

Vendor states this is fixed in 84b5cb476903003ae9ca88f32b57ff0eaefa6d4c (fixed)

Vendor states this is fixed in 86ce0e93cf6fb4d0c447323ac66577c642628b9d (fixed)

Vendor states this is fixed in 925cb538bd5851154602818dc80bf4b4d924c127 (fixed)

Vendor states this is fixed in aae35a0c8a775fa4afa6a4e7dab3f936f1f89bbb (fixed)

Vendor states this is fixed in db333ae981fb8843c383aa7dbf62cc682597d401 (fixed)

Vendor states this is fixed in 3.12 (unaffected)

Vendor states this is fixed in 4.14.299 (unaffected)

Vendor states this is fixed in 4.19.265 (unaffected)

Vendor states this is fixed in 4.9.333 (unaffected)

Vendor states this is fixed in 5.10.154 (unaffected)

Vendor states this is fixed in 5.15.78 (unaffected)

Vendor states this is fixed in 5.4.224 (unaffected)

Vendor states this is fixed in 6.0.8 (unaffected)

Vendor states this is fixed in 6.1 (unaffected)

Remediation

No guide yet

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

Patch and advisory references