NFSv4.1: zero referring call lists before decoding
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4aece6a19cf7f474f15eb861ba74db4479884ce3 · < 8fa4804fe62ca4155a2d8fc2789d630376cbf2fc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSv4.1: zero referring call lists before decoding
decode_cb_sequence_args() allocates csa_rclists with kmalloc_objs(), so each referring_call_list starts uninitialized. decode_rc_list() assigns rcl_refcalls only when rcl_nrefcalls is nonzero. A valid list with zero referring calls therefore leaves the pointer uninitialized, and nfs4_callback_sequence() later passes stale slab contents to kfree().
Allocate csa_rclists with kzalloc_objs() so every rcl_refcalls member is NULL from the beginning, including valid empty referring call lists.
From the CVE record · Linux
The Linux kernel leaves a pointer uninitialized when decoding an NFSv4.1 callback sequence with a valid, empty referring call list. Processing that sequence can pass stale memory contents to kfree(). The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with NFSv4.1 callback support should check their kernel versions; affected versions are not specified.